Re:When deployments are easy, code becomes simpler
by OJFord on Wednesday September 06, 2023 @07:40AM
(#37403695)
In what sense is 'downgrade' not just that prepared ahead of time? Or do you just not like the name?
Of course usually it would be followed by something that fixes it 'properly' - applying the original 'upgrade' again but with some correction, but typically that'll take longer than reverting to the previous version, and given it's gone wrong you'll probably want to take longer with it, test more, restore confidence.
Re:When deployments are easy, code becomes simpler
by perrygeo on Wednesday September 06, 2023 @10:09PM
(#37413878)
downgrade implies that such a thing is possible. In a stateful system though, you cannot take back that which you have committed. It's quite literally impossible by definition.
Re:When deployments are easy, code becomes simpler
by OJFord on Thursday September 07, 2023 @03:48PM
(#37424613)
No it isn't?
Forward migration: add date column, set = date(day, month, year) for existing records, drop is valid date constraint, drop day/month/year columns
Down migration: add day/month/year columns, add is valid date constraint, set day/month/year = appropriate datepart of date, drop date column
for trivial example.
Re:When deployments are easy, code becomes simpler
by tianzhou on Wednesday September 06, 2023 @10:08AM
(#37405385)
>> This is why I've never used or understood the value of the "downgrade" feature in some database migration tools
It's technically a roll forward, while to most users it's more nature to say rollback/revert
Re:When deployments are easy, code becomes simpler
by grecy on Wednesday September 06, 2023 @02:47PM
(#37409351)
It’s moving forward to get back to where you started
Re:When deployments are easy, code becomes simpler
by nicoburns on Wednesday September 06, 2023 @04:41PM
(#37411014)
I’ve found “downgrade” mostly useful for quick iteration during local development (where you may well not care about lost data). Realise your initial cut of the migration wasn’t quite right? Run “down” then fix it, then “up” again.
This is why I've never used or understood the value of the "downgrade" feature in some database migration tools. If you need to revert, make a _new_ migration that fixes the problem. Your tooling/code/logs should reflect the true history of the system without cooking the books.