[sqlalchemy] Re: MySQL DDL broken with autoincrement-column in multipart-key using InnoDB

Aug., 17:53, Michael Bayer mike...@zzzcomputing.com wrote: Christian Schwanke wrote: Hi Michael, thanks for your quick reply (again). I'm currently on the 0.6 branch after I ran into the first problem a few days ago but in my actual schema, the autogenerated ID in the second PK-column

[sqlalchemy] MySQL DDL broken with autoincrement-column in multipart-key using InnoDB

I'm using MySQL and want to use a combined primary-key where the second column is autogenerated while the first part is an assigned value. This is how my Table-definition looks like: table_a = Table('table_a', metadata, Column('assigned_id', Integer(), primary_key=True, autoincrement=False),

[sqlalchemy] Re: MySQL DDL broken with autoincrement-column in multipart-key using InnoDB

Hi Michael, thanks for your quick reply (again). I'm currently on the 0.6 branch after I ran into the first problem a few days ago but in my actual schema, the autogenerated ID in the second PK-column is referenced by another table that is mapped as a one-to-many relation. When persisting the

[sqlalchemy] Re: Problems with composite primary key and nested relations

Hi Michael, thanks for your effort, glad to hear that the issue is resolved! On 1 Aug., 02:37, Michael Bayer mike...@zzzcomputing.com wrote: On Jul 31, 2009, at 7:20 PM, Michael Bayer wrote: I will investigate a way such that the dialect more intelligently selects the primary key column

[sqlalchemy] Problems with composite primary key and nested relations

Hi, I've ran into a problem when using a composite primary key with auto_incremented values and nested relations. My scenario is as follows: I have three models A, B and C, where A has a one-to-many relation to B and B has a one-to-many relation to C. A has a standard primarykey consisting of