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 model with an entry in the unsaved relation, the generated id is not "cascaded" to the related item, when autoincrement is set to False on the id column (using the execute_at solution to fix the table definition). I will post the DDL-Part on the trac-bugtracker.
Since the DDL-Patch works for me and the ID is then correctly set during flush, this is not a show stopper but it seems to me, that in the 0.6 version, the autoincrement flag does affect more than the DDL generation. Anyways, thanks for your help and effort! Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
