There's whole religions dealing with table-naming conventions. For instance, I'm in the "table names are singular" sect. My other conventions are: prepend table names with project name/abbreviation. (We do this because we'll have multiple projects in the same DB, which in itself is not a best practice.) Do not prepend column names with table name (except the ID column) Use "standard" column names for look-up tables (i.e., all the descriptive "title" columns are called "title" or "name" - not "type," "color" etc. This lets you do some things dynamically with your administrative tools, if you want. On the other hand, it means aliasing table names if you're joining. I don't mind aliasing, so that's how I do it.
-d ----- Original Message ----- From: "Andrew Dixon" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Tuesday, October 19, 2004 6:30 AM Subject: OT: Field Naming > Hi Everyone. > > I'm just starting a major project for a government client and the > first job is to design the database. Is there any recongnised > convention on the naming of database fields. In the past I have always > named them [table_name_field_name] for example: projects_id where the > table is called 'projects' and the field is called 'id'. > > Thanks in advanced. > > Best Regards > > Andrew. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Sams Teach Yourself Regular Expressions in 10 Minutes by Ben Forta http://www.houseoffusion.com/banners/view.cfm?bannerid=40 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:181827 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
