Re: [sqlalchemy] Constraint naming conventions and MySQL's 64 character name limit

2015-04-12 Thread Giovanni Torres
On 11 Apr 2015, at 01:00, Mike Bayer mike...@zzzcomputing.com wrote: On 4/10/15 4:55 PM, Giovanni Torres wrote: CREATE TABLE foobar ( id INTEGER NOT NULL AUTO_INCREMENT, CONSTRAINT pk_foobar PRIMARY KEY (id) ) need a test case illustrating the failure. The main problem

Re: [sqlalchemy] Constraint naming conventions and MySQL's 64 character name limit

2015-04-10 Thread Giovanni Torres
On 10 Apr 2015, at 00:56, Mike Bayer mike...@zzzcomputing.com wrote: On 4/9/15 3:38 PM, Giovanni Torres wrote: Hello All! I'm facing the well known problem of maintaining constraints, when using sqlalchemy (v0.9.8), alembic (v0.7.4) and MySQL (v5.5.41) on Ubuntu (v14.04.2). I'm

Re: [sqlalchemy] Constraint naming conventions and MySQL's 64 character name limit

2015-04-10 Thread Mike Bayer
On 4/10/15 4:55 PM, Giovanni Torres wrote: CREATE TABLE foobar ( id INTEGER NOT NULL AUTO_INCREMENT, CONSTRAINT pk_foobar PRIMARY KEY (id) ) need a test case illustrating the failure. The main problem with this is that I can’t see a way to modify primary keys with alembic in a

[sqlalchemy] Constraint naming conventions and MySQL's 64 character name limit

2015-04-09 Thread Giovanni Torres
Hello All! I'm facing the well known problem of maintaining constraints, when using sqlalchemy (v0.9.8), alembic (v0.7.4) and MySQL (v5.5.41) on Ubuntu (v14.04.2). I'm talking specifically about these two links: o