News for hackers. Stuff that matters.

A comment on Database schema changes are hard (2017). Parent comment

Re:Database schema changes are hard (2017) by jayd16 on Friday March 01, 2019 @11:42PM (#19287608)
I would say this is a pretty limited view. If you're working on a large team with many non production environments, this style is far more cumbersome than the upgrade chain method.

If we're talking about deployed sqlite dbs running on client machines, expecting an upgrade to be a manual process is simply not acceptable.

[ Parent | on HN ]
Re:Database schema changes are hard (2017) by djrobstep on Friday March 01, 2019 @11:59PM (#19287649)
What makes it more cumbersome?
[ Parent | on HN ]
Re:Database schema changes are hard (2017) by jayd16 on Saturday March 02, 2019 @12:04AM (#19287668)
If I'm understanding correctly, the suggestion is to run the migration by hand and handle issues as they arise. Not nearly as nice as an automated migration.
[ Parent | on HN ]
Re:Database schema changes are hard (2017) by djrobstep on Saturday March 02, 2019 @03:13AM (#19288223)
The talk is more about creation migration scripts than deploying them, but definitely not suggesting doing anything by hand. The idea is to ensure correctness so you can automate the deployments with confidence.
[ Parent | on HN ]