Sounds like the "invalid cursor state" bug that I thought might have been
fixed for pyodbc in r2729. Maybe not...
Try adding the keyword parameter
use_scope_identity = False
to the create_engine() call and see if that clears it up.
On 6/15/07, che <[EMAIL PROTECTED]> wrote:
>
>
> forgot to mention that SA is at revision r2733.
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
