> create a new database and was about to name my primary key field. In the
> past, I've based the name on the table name, ie on table orders, order_id.
> Sometimes that results in some long field names. So, does anyone see a
> downside to naming it a simple "id" or maybe "rowid" or "r_id" or something
> similar?
The standard that I use is to have table names pluralized except in
the case of join tables (users, locations, userslocations) and then
will generate the ID based on the table name (users_id, locations_id,
userslocations_id).
Yes it can lead to long field names, however it makes for easier to
follow standards.
Hatton
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
