Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 1
    So, all of your options have their place. Can you talk more about what your objectives are, what you're trying to optimize for, etc? As it stands, answers have to be kind of opinion-based w/o you giving some parameters on which to judge the best option. Commented Aug 23, 2018 at 19:14
  • Looking into multi-tier frameworks like ocsigen could be inspirational Commented Aug 23, 2018 at 19:25
  • Option #4 is to denormalize the tables using views. A good ORM will still allow you to map a class to a view in the database, although you can't do inserts, updates or deletes without jumping through some additional hoops. Commented Aug 23, 2018 at 20:23
  • 4
    Suppose you denormalize the user-ids into user names and then a user changes their name. Would you then update all previous tweets with the name change, or would you accept that that person is suddenly no longer tagged in the older tweets (which could be just a few seconds old). Commented Aug 24, 2018 at 7:33
  • As @BartvanIngenSchenau alludes to, denormalization is associated with a lot of problems. Is there a specific reason you are considering it? Commented Aug 24, 2018 at 17:09