Re: Is "name" a keyword?
- From: "Cecil" <cecilkain0@xxxxxxxxx>
- Date: 28 Dec 2005 04:50:55 -0800
OK, can you help me to understand why ID and name are poor field
choices. I am asuming it has to do w/ ambiguity. I always qualify
fields w/ their table names for precisely this reason, so I always
concidered something like Category.categoryID to be very redundant.
I prefer Category.ID and Category.name. The only time I would write
CategoryID is if it was a foreign key linking to the "ID" field in the
Category table.
If you believe this to be poor practice, would you please explain why?
Thanks.
.
- Follow-Ups:
- Re: Is "name" a keyword?
- From: David Portas
- Re: Is "name" a keyword?
- References:
- Is "name" a keyword?
- From: Cecil
- Re: Is "name" a keyword?
- From: David Portas
- Is "name" a keyword?
- Prev by Date: Microsoft Distributed Blank CDs for Sqlserver 2005 and MSDN Library at Launch??
- Next by Date: Index for username/password
- Previous by thread: Re: Is "name" a keyword?
- Next by thread: Re: Is "name" a keyword?
- Index(es):