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
Ronan Lucio wrote:
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)
Ruslan,
IMHO:
1) Table name as prefix is unnecessary for me. It's norwegian notation
which I hate.
2) Also I recomend look into ANSI SQL standard for reserved keywords.
I've got experience of porting DB from MySQL(allow some keywords) to
another DB, it's pain.
Thank you your answer.
Do you
Harald,
I don't see the necessity of the latter naming scheme since
SELECT cod, name, description FROM car
can also be written as
SELECT car.cod, car.name, car.description FROM car
Do you know how it would be about portability?
Thanks,
Ronan
--
MySQL General Mailing List
For list
Harald Fuchs wrote:
In article [EMAIL PROTECTED],
Ronan Lucio [EMAIL PROTECTED] writes:
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
