Hi Michael,
the problem does not occur, when the autoincrement is set to True, so
your fix works correctly.
The problem of the generated id not being set only turned up again,
when I was experimenting with autoincrement=False (to fix the dialect
problem at table creation time) in conjunction
Christian Schwanke wrote:
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(),
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
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 is referenced by another table that is mapped as a
one-to-many
