I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
1a. Use singular names for tables unless you have a Really Good Reason™.
1b. Don't use keywords for table names.
1c. Don't say 1b doesn't matter because you'll quote everything. Just don't.
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I'm not sure it's agreed to use singular names.
At least in Sql-Server it's not a common practice.
The logic is:
Table contains many records, each record is single, but the table is a collection.
So "Users" because it contains multiple records of "User".
Currently developing futuristic smart-device, IoT connected, highway construction site safety system in EU.
Used to work on infrastructure, application architecture and cloud engineering.
I think because most ORM frameworks do pluralization so your table Users would eventually become Userses if the framework does not include any english stemming algorithm.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
1a. Use singular names for tables unless you have a Really Good Reason™.
1b. Don't use keywords for table names.
1c. Don't say 1b doesn't matter because you'll quote everything. Just don't.
Ok, so I'll revise this: stick to the singular/plural decision made by the framework you're using.
My main concern is that people aren't good at pluralising things and some things are done naively by code, such as "family" becoming "familys".
I'm not sure it's agreed to use singular names.
At least in Sql-Server it's not a common practice.
The logic is:
Table contains many records, each record is single, but the table is a collection.
So "Users" because it contains multiple records of "User".
Why singular names?
I think because most ORM frameworks do pluralization so your table
Userswould eventually becomeUsersesif the framework does not include any english stemming algorithm.