yeah, this is a feature Daniel Miller has requested as well since he had this issue. its tricky for the ORM to detect this condition on its own (and merging unique columns into the primary key would definitely not be appropriate. if you want that for your case, you can just send the primary_key argument to mapper and specify the composite key yourself).
in your case , SA issues INSERTs before DELETEs and its not getting that far since your constraint is failing. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
