DB migrations WAS19 #2
firepear
commented
Owner
- Use a version field to the meta table to drive migrations
- Migrations should happen at catalog initialization
- Driven by a dispatch array -- all elements of the array with an index greater than the value of version should be run
- Array elements should contain the migration function itself and a description, to be printed/logged at migration time
- Each migration function should simply returns error. Any value other than nil should be considered a failure
- Use a version field to the meta table to drive migrations
- Migrations should happen at catalog initialization
- Driven by a dispatch array -- all elements of the array with an index greater than the value of version should be run
- Array elements should contain the migration function itself and a description, to be printed/logged at migration time
- Each migration function should simply returns error. Any value other than nil should be considered a failure
firepear
self-assigned this
firepear
added this to the (deleted) milestone
firepear
modified the milestone from (deleted) to v0.21
firepear
removed this from the v0.21 milestone
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?