What is the best practice in naming your "user" table?

Question

Here's three best practices I try to follow when naming tables:

• Never name a table with plural (such as "users")
• Never name a table using a reserved keyword (such as "user")
• Never prefix your table name with "tbl" or some other object type prefix

Keeping all this in mind, how do you recommend naming the table that will hold user identities?

Answer 1

I agree, do not use any reserved words, or quoted or bracketed or escaped forms of reserved words.

Name the User table Person.

You may be interested in this answer and google for the ISO standard 11179 for naming Guidelines

Answer 2

I typically use something like member or account, depending on the application. That said, if you're using modern design tools and principles (e.g., a db abstraction layer or ORM with an object-oriented code base that separates business logic from data access), then table naming becomes fairly irrelevant. Your developers should only ever be accessing the database through a well-defined interface and not by hand-writing SQL that requires them to know the table name. For example, you could name the table account but map access to it via an object named User. Your developers shouldn't be thinking in terms of tables, but in terms of access objects, which aren't going to have the same restrictions on naming:

$user = new User($username); $user->authenticate($password);