4 ms·

This only works if database changes are backwards compatible which is not always the case. In all other cases you're procedure seems only reasonable. I don't u

This only works if database changes are backwards compatible which is not always the case. In all other cases you're procedure seems only reasonable. I don't understand why anyone would do it differently.

tonyarkles 11y ago
That's the trick: transform all database changes to be backward compatible between version n and n+1. It takes a little more time, and you end up with multiple deploys, but it's really quite nice.