On 11/19/2015 04:01 AM, Chris Frey wrote: > On Wed, Nov 18, 2015 at 11:23:11PM -0500, Mike Bayer wrote: >> if you change your naming convention, then that would show up as a bunch >> of brand new constraints in the model and a whole bunch of constraints >> removed in the model, so in theory would produce a lot of add constraint >> / drop constraint instructions. > > Thanks for your reply Mike! > > I probably didn't explain my steps very clearly, but what I was trying > to achieve was basically what you state above. > > And if I run a test, changing my foreign key naming convention from: > > "fk": "fk_%(table_name)s_%(column_0_name)s", > > to > > "fk": "fkk_%(table_name)s_%(column_0_name)s", > ^^^ > > I get no changes in the autogenerate script at all. > > And when I say changes, for constraints, I am indeed expecting drop/add, > as you explained.
yup this would need to be some kind of custom autogenerate recipe for starters, with the key being how to indicate a table that's been renamed vs. added and dropped. > > Thanks, > - Chris > -- You received this message because you are subscribed to the Google Groups "sqlalchemy-alembic" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy-alembic+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
