Andreas,
I don't know of a standard for naming such things. My advice is to group
your table names with a prefix if they are related to one another. Name
fields in such a way that the field's *purpose* is clear to you;
e.g.-"checked_out_by", "checked_out_date", "is_checked_out", etc. Make sure
foreign keys are named in such a way that 6 months down the road you will
clearly be able to figure out what table they reference. I've never felt
the need to append the type of the field onto its name; after all, that is
what the describe statement is for. ;)
-Rob
-----Original Message-----
From: Andreas [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2003 10:34 AM
To: [EMAIL PROTECTED]
Subject: standardized naming system ?
Hello list,
is there a common naming system for db objects ?
Like:
1) Tables: mytable, tblmytable, tbl_mytable
2) Indices: idx_anindex
3) Columns: int_somenumber, date_lastupdate
4) id for the numerical primary key e.g. table customers.id
and then for referencing foreign keys
table addresses : addresses.customer_id or addresses.customer_fk
OK, I know I could name them the way I want but perhaps there is some
kind of common sense in this regard ?
... A.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
