Hi, The MSSQL users on here may recall earlier threads about SQLAlchemy fetching the wrong IDs for inserted rows, in situations where the table has a trigger that causes another insert.
With a lot of help from Michael Jahn, I have just committed a fix so that SA can use scope_identity with PyODBC. You have to use a modified version of PyODBC; Windows binaries are available on ticket #537 and the patch will hopefully be applied to the main PyODBC at some point. This is only enabled if you set ?use_scope_identity=1 in the DBURI. And if you set that with unmodified PyODBC, you will get all sorts of errors :-) Regards, 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 -~----------~----~----~----~------~----~------~--~---
