On May 22, 8:37 pm, schickb <[EMAIL PROTECTED]> wrote: > Maybe SA is putting second execute in a transaction that isn't > being commited?
That was the problem. I found this in the SA docs: "While many DBAPIs implement a flag called autocommit, the current SQLAlchemy behavior is such that it implements its own autocommit. This is achieved by searching the statement for strings like INSERT, UPDATE, DELETE, etc. and then issuing a COMMIT automatically if no transaction is in progress." I fixed the issue by wrapping the execute with trans = dbconn.begin() before and trans.commit() after. Seems like the decision to autocommit raw sql statements would be better left to the DBAPIs since they know more about non-standard sql statements like COPY. -Brad --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
