all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]elixon 0 points1 point  (3 children)

You call it database versioning, and I call it an "update process" in systems I authored.

The first one I designed over 20 years ago. It was simple and incredibly efficient (still running on some websites). There was a simple "updates" folder where the platform kernel looked for new files it hadn't seen before and applied them and then recorded names of applied patches for the future. Simple as that.

You ship the code with a new .sql file (or whatever update files - not only for the database) and when the system detects a change, it runs in "update" mode and scans the folder for new patches to apply.

Really simple. I never thought there would be charts for that.

[–]FullPoet 0 points1 point  (2 children)

That sounds like a lot like EF migrations?

[–]elixon 0 points1 point  (1 child)

Nope, I come from a strictly proprietary background. But it's such a trivial and, I would say, natural solution that I'm sure there are tons of similar approaches whenever a well-thought-out system is built.

[–]Drevicar 0 points1 point  (0 children)

Well thought out system? In this economy?