5 ms·
I'd like to know what I am doing wrong, as I use migrations all the time. The option is change the database later (and use migrations) or write a whole ton of c
by collyw 10y ago
I'd like to know what I am doing wrong, as I use migrations all the time. The option is change the database later (and use migrations) or write a whole ton of crappy code to avoid using them. I have tried both ways and usually migrations work better.
- tinix 10y agoI dunno what to tell you without specific details about your application and environment in general. Clearly, you need a better system architecture if you're having to do migrations constantly.
- tobltobs 10y agoI always thought a data model should be as agnostic to the system architecture as possible. Insofar I don't understand how a system architecture can help to avoid data model migrations.
- tinix 10y agoData structure, both storage, and in-memory, are very much a part of architecture.
- collyw 10y agoSo requirements are never added / changed in your systems? Thats usually why I need migrations.