M
Marian Edu
Guest
the later of course 
I tend to use surrogate keys almost all the time for FK (wait, what the hell am I talking about... was that triggers, BL, DA, BPM, BRM) and that's because most of the time even things we think will never change actually does 
On 05/13/2014 02:10 PM, jmls wrote: From: jmls Post: composite foreign keys Posted in: OpenEdge Development Link: http://community.progress.com/technicalusers/f/19/t/10162.aspx As large and vitriolic discussions seemed to have died down recently and I have lost a source of entertainment, I thought that I'd throw this to the list ... I was having a discussion with a colleague today about having a foreign key that is multi-component index I questioned how common this would be , and the answer was "more common than you think" Surely this is inherently a bad database design ? After all, it violates TNF etc etc what's the consensus ? Have I been a pedantic db designer all my life ? Is there something that I am missing ? Or is it simply bad db design to have this sort of construct ? please say the latter ... 
-- You were sent this email because you opted to receive email notifications when someone created a new thread. To unsubscribe from: - ...only this thread, disable notifications at http://community.progress.com/technicalusers/f/19/t/10162.aspx. - ...all email notifications from Progress Community, navigate to "Settings", click on the "Email" tab, then under the "Email Configuration" section, set Send Notifications to "No". -- m.edu keep it simple http://www.ganimede.ro http://ro.linkedin.com/in/marianedu medu@ganimede.ro mobile: +40 740 036 212 skype: marian.edu
Continue reading...
I tend to use surrogate keys almost all the time for FK (wait, what the hell am I talking about... was that triggers, BL, DA, BPM, BRM) and that's because most of the time even things we think will never change actually does On 05/13/2014 02:10 PM, jmls wrote: From: jmls Post: composite foreign keys Posted in: OpenEdge Development Link: http://community.progress.com/technicalusers/f/19/t/10162.aspx As large and vitriolic discussions seemed to have died down recently and I have lost a source of entertainment, I thought that I'd throw this to the list ... I was having a discussion with a colleague today about having a foreign key that is multi-component index I questioned how common this would be , and the answer was "more common than you think" Surely this is inherently a bad database design ? After all, it violates TNF etc etc what's the consensus ? Have I been a pedantic db designer all my life ? Is there something that I am missing ? Or is it simply bad db design to have this sort of construct ? please say the latter ... -- You were sent this email because you opted to receive email notifications when someone created a new thread. To unsubscribe from: - ...only this thread, disable notifications at http://community.progress.com/technicalusers/f/19/t/10162.aspx. - ...all email notifications from Progress Community, navigate to "Settings", click on the "Email" tab, then under the "Email Configuration" section, set Send Notifications to "No". -- m.edu keep it simple http://www.ganimede.ro http://ro.linkedin.com/in/marianedu medu@ganimede.ro mobile: +40 740 036 212 skype: marian.eduContinue reading...