You have noting to lose and everything to gain, some of the data dictionary
performance (underlying selects would probably be faster if all values for
column_names were unique...It would sure make good sense in a
repository...Also why would your design have so many columns with the same
names in so many tables...3NF huh ? Doesnt work for me...
John Seitz wrote in message <36D205DF.C69E6D01_at_pobox.com>...
>Its been a couple of years since my Intro to Relational DB by Cobb, but
>I'm a little stumped.
>A person at work today told me that I should never have duplicate
>column/field names in different tables unless they are relationships.
>
>Am I on the pipe to think this person is crazy. There is only so many
>ways to have a column called CITY or ZIPCODE. Should I be putting the
>tablename in front of it like CUSTOMER_CITY?
>
>Any help would be appreciated. We will be fighting about this for days.
>
>John Seitz
>
>
Received on Tue Feb 23 1999 - 15:15:22 CST
