> The last argument above is the strongest, because it only takes one such exception to wreck an entire schema’s consistency. The last argument: > Some relati

> The last argument above is the strongest, because it only takes one such exception to wreck an entire schema’s consistency. The last argument: > Some relations are already plural. Say you have a class called UserFacts that store miscellaneous information about a user, like age and favorite color. What will you call the database table? I lean towards thinking this is a non-issue. In this specific case I'd actually call the model UserFact and the table users_facts. I'd assume it maps many users to many facts. It otherwise sounds like there's some json or "text" (as in "ADD COLUMN my_column TEXT") data that is storing words as "facts" and the table name is just kinda weird. I don't see the problem and if someone were to insist there's a problem, I'd probably suggest changing the model name.