Re: Using alembic with two projects, one with foreign keys referencing the other

2016-09-29 Thread Wesley Weber
Thursday, September 29, 2016 at 9:46:59 PM UTC-4, Mike Bayer wrote: > > > > On 09/29/2016 07:52 PM, Wesley Weber wrote: > > I have an uncommon use case that might or might not be supported (or > > even a good idea): > > > > I have a main, independent project

Using alembic with two projects, one with foreign keys referencing the other

2016-09-29 Thread Wesley Weber
I have an uncommon use case that might or might not be supported (or even a good idea): I have a main, independent project with its own tables. I would like to keep track of migrations of its database. I will also have several "plugin" projects, which can add functionality to the main software.

NotImplementedError: No generic 'DROP CONSTRAINT' in MySQL

2013-12-29 Thread Wesley
urn fn(element, compiler, **kw) File "/usr/lib/python2.6/site-packages/alembic/ddl/mysql.py", line 138, in _mysql_drop_constraint "No generic 'DROP CONSTRAINT' in MySQL - " NotImplementedError: No generic 'DROP CONSTRAINT' in MySQL - please

NotImplementedError: No generic 'DROP CONSTRAINT' in MySQL

2013-12-29 Thread Wesley
urn fn(element, compiler, **kw) File "/usr/lib/python2.6/site-packages/alembic/ddl/mysql.py", line 138, in _mysql_drop_constraint "No generic 'DROP CONSTRAINT' in MySQL - " NotImplementedError: No generic 'DROP CONSTRAINT' in MySQL - please