Simon Willison wrote:
The other one is database table names. I would argue that since these are almost /never/ directly exposed in Django itself, they should be left as singular as well (just the name of the model class casted to lower case. If we wanted to be really radical we could leave them Titlecased!). This is bound to upset a lot of DB style purists (myself included) but the solution is there already: use the db_table model parameter to override it.
I'm in favor of depluralisation. This idea gives me an impression like I always wanted it myself :-)
I'm not very deep into databases but I should say that in two jobs where I worked with DBs more or less closely there were a strict rule to always name tables in singular form. Of course what really matters is the uniform convention that everyone should use. But singular form still seems to me better since there can be no variations (like 'people' or 'children') and one can always use a model name as a table name.
