I'm using plural because it is a better fit for the mental model behind tables (or relations or sets). In a table you store many employees, not a single one.
In object oriented programming, on the other hand, it makes sense to use singular names for classes because the each instance only stores one employee (for example). In that context plural only makes sense when having a collection of employee objects.
Quite often, using the wrong numerus (plural/singular) indicates a wrong understanding of the underlying principles. In SQL you always work we sets that happen to have only one member sometimes—still it is a set :)
answered
Jul 31 '14 at 11:50
Markus Winand ♦♦
936●5●11●20