Menu
▾
▴
#53 Database Backfill
This feature would reduce the need for manual upgrade scripts.
Basically, its a "population-default". Sometimes you add a column to the database that is not null and has no default. However, you want to give all existing rows in that database one value for that column, or a simple calculation of that value. So the data dictionary needs to know what that value is when it has to add it or make it not null for upgrades.
Potential automations:
* SUM
* COUNT
* FETCH (arbitrary query? is this yaml or sql)
* This could exist alongside a "real" default. basically, the upgrade script would add the column, run the script on the null values, and then add the default.
* A single static value (in my experience theres usually a "before I added this column" value.
Questions:
* What about AUTO-INSERT foreign key tables? We would actually have to generate all of the rows in the table.
This one will be really cool, but involves a lot more changes to the builder than it might seem. Let's leave this to Release 2, when we will be refactoring the builder.