[thelist] SQL: database/table design
Tab Alleman
Tab.Alleman at MetroGuide.com
Mon Jun 7 10:18:15 CDT 2004
Colin Gremillion wrote:
> Anyway, my manager hated this idea, and suggested that
> I make a new table, where each event-speaker
> relationship would have a record. So I now have this
> table with three fields: "SpeakerID" (linked to
> "speakers"), "EventID" (linked to "seminar") and
> "SpeakerType" which says if they're "primary" or
> "secondary".
This is exactly how I would have handled it as well; it is the
recommended approach in all the books I've read.
More information about the thelist
mailing list