Re: Same Column names in different tables?

The main reason is to spill tables up/unnormalize them. The software is a huge medical directory. So I have companies, people, doctors, hospitals... and a lots of other entity that all have Addresses. I know that I could have added a column called type to one ADDRESS table, but that will slow my queries down a lot. I'm looking at a 10gig DB so I'm trying to get as much out of it as possible.

Also, about 5 tables have the field called Description. This is in the product, DXCode, service tables. So I don't see the reason why I would want different names.

John

Adrian wrote:

> 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 - 19:30:27 CST