Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.mysql > #6051
| From | Thomas 'PointedEars' Lahn <PointedEars@web.de> |
|---|---|
| Newsgroups | comp.databases.mysql |
| Subject | Re: Design-stage advice and opinions welcomed |
| Date | 2015-09-26 15:16 +0200 |
| Organization | PointedEars Software (PES) |
| Message-ID | <1618465.feeTcn2y4M@PointedEars.de> (permalink) |
| References | <d6i203Frj62U1@mid.individual.net> <71dztw7u5cuf$.16wg337gsku0z.dlg@40tude.net> <F_GdnWoMTc1tUZjLnZ2dnUU7-ROdnZ2d@posted.internetamerica> |
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: @PointedEars2
Please do not cc me. / Bitte keine Kopien per E-Mail.
Back to comp.databases.mysql | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Design-stage advice and opinions welcomed Derek Turner <frderek@suremail.je> - 2015-09-24 10:35 +0000
Re: Design-stage advice and opinions welcomed Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-09-24 22:58 +0200
Re: Design-stage advice and opinions welcomed Derek Turner <frderek@suremail.je> - 2015-09-24 21:15 +0000
Re: Design-stage advice and opinions welcomed Jerry Stuckle <jstucklex@attglobal.net> - 2015-09-24 17:53 -0400
Re: Design-stage advice and opinions welcomed Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-09-25 04:57 +0200
Re: Design-stage advice and opinions welcomed Geoff Muldoon <geoff.muldoon@trap.gmail.com> - 2015-09-25 13:15 +1000
Re: Design-stage advice and opinions welcomed gordonb.lizck@burditt.org (Gordon Burditt) - 2015-09-25 17:38 -0500
Re: Design-stage advice and opinions welcomed Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-09-26 15:16 +0200
Re: Design-stage advice and opinions welcomed Geoff Muldoon <geoff.muldoon@trap.gmail.com> - 2015-09-28 09:46 +1000
Re: Design-stage advice and opinions welcomed Derek Turner <frderek@suremail.je> - 2015-09-28 03:34 +0000
Re: Design-stage advice and opinions welcomed Derek Turner <frderek@suremail.je> - 2015-09-28 03:27 +0000
Re: Design-stage advice and opinions welcomed Jerry Stuckle <jstucklex@attglobal.net> - 2015-09-27 23:53 -0400
Re: Design-stage advice and opinions welcomed Derek Turner <frderek@suremail.je> - 2015-09-28 10:46 +0000
Re: Design-stage advice and opinions welcomed The Natural Philosopher <tnp@invalid.invalid> - 2015-09-28 12:57 +0100
Re: Design-stage advice and opinions welcomed Jerry Stuckle <jstucklex@attglobal.net> - 2015-09-28 09:41 -0400
Re: Design-stage advice and opinions welcomed bill <william@TechServSys.com> - 2015-09-29 07:14 -0400
csiph-web