3 ms·
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 generate
by StavrosK 9y ago
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.
- threeseed 9y agoFor 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.
- zaarn 9y agoIf 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.
- StavrosK 9y agoHow do schemaless databases make this easier?
- saiya-jin 9y agoImagine a core banking system system migration - few TB of data, few thousand of tables, various background processes for different purposes over them, 0 margin for error. Usually 10-20 people working on dev side, same amount of testing. Impossible to not have issues. If you say you deliver these kind of projects with 1 command, then we're talking about very different scales of projects (mine is rather 100 page runbook for DB admins)