Marcello (md9@ibest.com. br) writes:
I'm not surprised. :-)
For very common attributes like name, id, code and so on, I typically
include something related to the table, so that you have product_name,
customer_id, currency_code and so on. But prefixing every column is
useless in my opinion. It only adds noise.
Also, I want the same entity to normally have the same name in all tables
it appears. That is, it's customer_id in the customers table as well
as the orders table, and not order_customer_ id in the latter table.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se
Books Online for SQL Server 2005 at
Books Online for SQL Server 2000 at
I spent my whole Sunday reading database naming conventions,.
And this only made me more confused.
And this only made me more confused.
One thing that I do in my tables was one of the more “allways avoid”
one.
I allways prefix the column name with a prefix that identifies the
table where It resides.
>...
>
So "My Standard" is something like these
Prod_Name
Cli_Name
Prod_Id
Cli_Id
>
Is Just me?
one.
I allways prefix the column name with a prefix that identifies the
table where It resides.
>...
>
So "My Standard" is something like these
Prod_Name
Cli_Name
Prod_Id
Cli_Id
>
Is Just me?
include something related to the table, so that you have product_name,
customer_id, currency_code and so on. But prefixing every column is
useless in my opinion. It only adds noise.
Also, I want the same entity to normally have the same name in all tables
it appears. That is, it's customer_id in the customers table as well
as the orders table, and not order_customer_ id in the latter table.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se
Books Online for SQL Server 2005 at
Books Online for SQL Server 2000 at