3 ms·
For the versionning part there is usually tools in your language. For ex: Flyway for java, diesel_migration for rust ...
by Timshel 3y ago
For the versionning part there is usually tools in your language. For ex: Flyway for java, diesel_migration for rust ...
- sverhagen 3y agoI don't know... the places I've worked where there was that much of the application shifted into the database layer, there would be no Flyway. You'd be happy to get write permissions, let alone permissions to update the structure. Perhaps correlated, those organizations managed the versioning part through a heavy-handed change management process, ie. humans. Perhaps in some places it's cool now to do this, but for me having the entire application logic modeled in the database will always be associated with painful enterprise culture.
- draven 3y agoWe're already using Liquibase where I work (I don't remember exactly why it was chosen over Flyway.) I also worked at a company where every DB access had to be done with a stored proc. The stored procs would be reviewed by the DB team. They were versioned by using a version number in the name, like GetUsers_v1, and multiple versions could exist at any given time in the DB.