This is a follow-up to the design summit discussion about DB migrations.
There was concern about the undo-ability of some migrations. The specific
example cited was removal of a column. Could that be done with the
following three migrations, each undo-able? First, change the code to
keep writing the column but no longer read the column. Second migration
changes the code to neither read nor write the column. Third migration
physically removes the column.
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
