Re:What MongoDB got right (2015)
by StavrosK on Tuesday November 28, 2017 @05:19AM
(#15795917)
I have worked on tens of projects in the past decade, and I have very rarely seen migrations be anything other than automatic, taking one command to be generated.
[ Parent
| on HN ]
For basic schema changes maybe.
But often you are adding to reference data or running a transform SQL in order to produce some new denormalised table or the huge array of changes needed to support new use cases. These can't be automated and are hugely error prone.
If your Schema is properly setup after the initial changes to it, then it's not error prone at all, it's doing what it's supposed to do.
Unless you migration involves "disable all checks, add new columns/tables, move and delete old data, enable all checks"
If you are migrating to a denormalised table then it should obviously crash when your conversion tool is doing something wrong and the RDBMS just prevented it from succeeding in doing something wrong.
If your migration is actually error prone as in "mangling and corrupting" data I suggest you are doing something wrong and you probably disabled the safety checks in your RDBMS.