Join tables are a bit more difficult if you pluralize tables. For example at work we have table names like:
customers
customer_attributes
customers_labels
On one side you want to be consistent with the "customers" table you're joining to. On the other hand it reads weirdly to have an extra "s" in the middle of the table name.
After you've got three or so words in a table name it really becomes inconsistent and you can't really guess what they're called when writing code.
There are solutions of course: whether to use the "s" on join tables could be a policy documented somewhere and everyone, including new employees, could be made aware of it. But it's a problem you don't have if you use singular table names.
After you've got three or so words in a table name it really becomes inconsistent and you can't really guess what they're called when writing code.
There are solutions of course: whether to use the "s" on join tables could be a policy documented somewhere and everyone, including new employees, could be made aware of it. But it's a problem you don't have if you use singular table names.