To me, this is entirely a matter of personal choice - and the important thing is to pick a standard and stick to it. :)
I usually end up with a table called 'People' for arguments sake, which will have an abstract PK (auto increment int) called PeopleID (I always use the table name). I also capitalize each word (and all abbreviations), which is a habit from MSSQL programming - MySQL is case sensitive, which is worth remembering. I use underscores to indicate that a table is a 'glue' table - e.g. If each row in People can correspond to multiple rows in the table Jobs, and vice versa, I would create People_Jobs to describe the relationship between the two. There are a number of different methods that have been published, including 'Norwegian', I believe - and a bit of googling should turn up some info on these. :) Cheers, Matt > -----Original Message----- > From: Ronan Lucio [mailto:[EMAIL PROTECTED] > Sent: 27 April 2004 15:46 > To: [EMAIL PROTECTED] > Subject: Standard of Column Names > > Hello, > > I´m doing the planing for an application that will use > MySQL as database. > > So, I´d like to know your opinions about the standard > for the column names. > > Supposing that I should create a table named car. > Is it better to have either the column names (cod, > name, description) or (car_cod, car_name, car_description)? > > Thanks, > Ronan > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
