OpenDataServices / developer-docs

Documentation about how we get our work done. For internal use, but happy to share
Other
1 stars 0 forks source link

Start database page with table names #60

Closed odscjames closed 6 years ago

odscjames commented 6 years ago

Well ....

I have no strong reasons to argue that they should be singular - it's just always seemed clearer. You tend to deal with rows one at a time, and so the name should reflect what one row of a table is. For instance, if you have a table of cars each row is one car, so the table should be called "car". If dealing with a system where models mirror table names, you want the model to be "Car" to.

But I accept that is really getting down to a preference. If you all tell me plural, so be it :-)

BibianaC commented 6 years ago

+1 for singular for exactly what @odscjames says. If a model name is singular, it makes sense that the db table is also singular. I also don't have a strong opinion about it.

odscjames commented 6 years ago

but would be even better if we noted that this is Django's default behaviour.

So I'm guessing your comment on #63 would be "yes"?

odscjames commented 6 years ago

On merging this particular P.R., I'll tag @kindly and give him a few days to see if he wants to comment first ...