M
marian.edu
Guest
Basically all tables are somehow bound to store multiple records so why bother using the plural… you might think there could be just the ‘god’ table that only have one (true) record but in practice there can be zero or more records even there 
Have to agree that sometimes I use plural just to avoid conflicts with a keyword (both 4gl and sql) so ‘users’, ‘roles’, etc… if you’re fun on naming conventions, those are just exceptions (mine is more like French, full of exceptions). Bref, forget about naming conventions and just use common sense. Since we’re referring a property of one object there is no point in keep repeating the object name when referring to it’s properties (employee.firstName, employee.lastName, …) as a side effect the developers will sometimes be forced to fully qualify the table name which in my book is a good practice anyway. Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212
Continue reading...
Have to agree that sometimes I use plural just to avoid conflicts with a keyword (both 4gl and sql) so ‘users’, ‘roles’, etc… if you’re fun on naming conventions, those are just exceptions (mine is more like French, full of exceptions). Bref, forget about naming conventions and just use common sense. Since we’re referring a property of one object there is no point in keep repeating the object name when referring to it’s properties (employee.firstName, employee.lastName, …) as a side effect the developers will sometimes be forced to fully qualify the table name which in my book is a good practice anyway. Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212Continue reading...