Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m wondering what the best practice is for naming primary/unique keys in a database with many tables. Should you always just call each table’s primary key id or is ok to not have an id field in each table and just name each of them something1_id, something2_id, etc?
Whatever you do, pick one or the other and stick to that standard. There are pros and cons for each.
I prefer
SomethingIDbut other people prefer justID. In the system I work with there are well over a thousand tables and having the PK and the FK have the exact same names makes things easier.