On 18/11/13 18:46, Nikola Đipanov wrote: > 1) How can we make reviewing changes with db migrations more robust > > Since we use sqlalchemy-migrate to version our database, the package's > documentation [2] states how care needs to be taken when importing code > inside a db migration script. It seems like this can be taken care of > with a hacking rule that will fail the patch if anything outside a > subset of modules is imported and used. I might be missing an angle > where such an approach could cause issues, so feel free to comment in > replies. IIUC - this is something we might want to enforce even when/if > we move to using Alembic for migrations. >
Joe already put up a patch for this - still WIP though: https://review.openstack.org/#/c/57009 - so feel free to discuss there if you are interested. N. _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
