Hi, I thought the original impetus for scope_identity was not multiple execution > contexts, but rather things being fouled up for some users where they had > nested INSERTs being done via a trigger on the mapped table, and the > brain-dead SELECT @@identity_insert wasn't able to pluck out the correct PK. > Was there another reason I'm missing? >
You're right, that was the original motivation. I tried just changing @@identity for scope_identity(), which worked just fine on pymssql, but not on the other adapters. Did eventually get it working, but it involved pyodbc changes, that I was unable to do. Fortunately someone on the list volunteered, which was most appreciated. Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
