21 ms·

I'd call it users_facts. But that's just me.

• veonik 3y ago
  There's definitely some ambiguity there, that's a good point. I'd probably say that users_facts would be a to-many join table between users and facts, like if you had one row per fact and a multiple facts per user though that example doesn't really make sense here (could just have the FK exist in Fact and not need a join table). If UserFacts were stored in a table with multiple facts in one row about a single user, I would probably call that table user_facts. Would probably also be fine with running across either in any codebase (or even singular table names, for that matter! as long as it's consistent :D )
  • zepolen 3y ago
    user_facts if it's one to many users_to_facts if it's many to many
• deleted 3y ago
  [deleted]