Re:What ORMs have taught me: just learn SQL (2014)
by snuxoll on Monday June 27, 2016 @04:19AM
(#11984818)
If only people would listen to this advice. The number of times I have started a project by trying to think about the data model only to get told "just build the models, we can change it later" drives me insane. Code is easy to change, your data model is not once it is in production.
Re:What ORMs have taught me: just learn SQL (2014)
by spronkey on Tuesday June 28, 2016 @04:40AM
(#11992307)
Only if you use a single, concrete data model. If your domain supports the use of something like event sourcing, your "data model" is surprisingly easy to change. Or in this case, is = are, and data model = data models, and they're actually derived from your domain events, which can be replayed. At any time.
Re:What ORMs have taught me: just learn SQL (2014)
by spacecowboy_lon on Monday June 27, 2016 @04:09AM
(#11984786)
testify Brother/Sister Testify
A project with nontrivial data relationships should start with the data model, not with a code model superimposed on data. ORM leads to bad data models and performance problems that are unfixable.