Re: Design-stage advice and opinions welcomed

From: Thomas 'PointedEars' Lahn <PointedEars_at_web.de>
Date: Sat, 26 Sep 2015 15:16:29 +0200
Message-ID: <1618465.feeTcn2y4M_at_PointedEars.de>


Gordon Burditt wrote:

[restored attribution]

> Derek Turner wrote:

>> b) Will you ever need to check for group/venue/day clashes?  If so then
>> cross checking that will include 1st meeting for one group against both
>> 1st and 2nd for another will become complex.

>
> I would think that venue/day/time clashes would be more of an issue.
> Many venues have more than one time slot in a day for a meeting.
> Two groups might decide to meet together one time for a subject of
> common interest (e.g. a Raspberry Pi group and a Linux group, since
> the Raspberry Pi runs Linux), which is an exception to this.

venue:

  venue_id name


         1 Raspberry Pi discussion

meeting:

  meeting_id venue_id time_start time_end


           1         1  '2015-09-26 09:00'  '2015-09-26 12:00'
           2         1  '2015-09-26 13:00'  '2015-09-26 16:00'

group:

  group_id name


         1  Linux developers
         2  Raspberry Pi users

meeting_group:

  meeting_id group_id


           1         1  
           1         2
           2         1
 

> It just might be that the first meeting slot describes a meeting with
> a guest lecturer, and the second meeting slot describes a work session
> where the participants actually build something. Which type of
> meeting happens on the overlap date.

This, too, can be solved by handling the meetings separately, but belonging to the same venue.  

-- 
PointedEars

Twitter: _at_PointedEars2
Please do not cc me. / Bitte keine Kopien per E-Mail.
Received on Sat Sep 26 2015 - 15:16:29 CEST

Original text of this message