i was taught that if you find yourself with a many-to-many relationship, just make sure you go back and re-examine whether or not it's truly necessary.
but if it is necessary (and certainly, many times it is), then you would do your junction|cross-ref|intersection|whatever table to facilitate that relationship. On 12/7/05, Russ <[EMAIL PROTECTED]> wrote: > I took a course or two on database design and I don't remember anyone > teaching us to avoid cross ref tables. How else do you design a > many-to-many relationship? > > > > -----Original Message----- > From: Ray Champagne [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 07, 2005 12:35 AM > To: CF-Talk > Subject: Re: database table design consideration > > --snip-- > > I was always taught to avoid bridge (or cross ref) tables, because it > usually meant that you designed your data structure poorly. I > understand that it's unavoidable in some cases, I was hoping that wasn't > the case here. > > ---snip--- > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:226455 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
