Hi all, I have some question about fixing old DB migrations. If we are now in havana. And some broken migration was added in Havana. Why we are not able to fix it directly? Instead of chaining few lines, we should add new migration that do some magic. For example in this migration https://review.openstack.org/#/c/33127/19 We have add unique constraint with wrong name, And it won't work properly in psql and mysql. Because of "strange" rule don't touch old migrations in any case we have to write one more migration: https://review.openstack.org/#/c/37251/ that recreate this unique constraint with correct name. Probably we should rethink this rule? Best regards, Boris Pavlovic Mirantis Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130718/92b47049/attachment.html>