Sounds good...thanks Kerry! Rick
> -----Original Message----- > From: Kerry [mailto:[EMAIL PROTECTED] > Sent: Friday, April 15, 2005 6:25 AM > To: CF-Talk > Subject: RE: Database Normalization Question > > > just a small point, the 2 table system does allow for > one-to-many, the link > table is only required for many-to-many. > > position_id,position_name > 1,Helpdesk Analyst > > employee_id,position_id > 1,1 > 2,1 > 3,1 > 4,1 > > > Now we have one position, with 4 employees, one to many. > > In this situation, I would go for the link table, because its much more > flexible for the future, e.g. if the client changes their organisational > structure > > > position_id,position_name > 1,Helpdesk Analyst > 2,Desktop Tech > > > employee_id,position_id > 1,1 > 2,1 > 2,2 > > employee_id > 1 > 2 > 3 > 4 > > > -----Original Message----- > From: Rick Faircloth [mailto:[EMAIL PROTECTED] > Sent: 14 April 2005 20:53 > To: CF-Talk > Subject: RE: Database Normalization Question > > > Well...if it was a one-to-one relationship always, and I had a two-table > db design, it would work, because I could simply update the employee's > profile and use a drop-down to reassign the position. > > But, if a one-to-many relationship could exist in the > organization, I would > need that three table, double-field primary key design... > > Right? > > Rick > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:203020 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=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
