I bumped up the [logger_sqlalchemy] to DEBUG and noted that COMMIT is
not called in the scenario under discussion.  I also confirmed that
the "COMMIT" string does get logged when appropriate.

The implication being that "COMMIT" string does appear in logger when
appropriate, and in the current scenario "COMMIT" is not appearing,
indicating that there is no COMMIT occurring, yet the transaction is
not rolling back.

If I come across further info, I will update this thread.  If anyone
else any other suggestion, kindly post.

Thanks.

On Sep 9, 4:50 pm, ozwyzard <[email protected]> wrote:
> I have posted a query on the sqlalchemy group.
>
> http://groups.google.com/group/sqlalchemy/browse_thread/thread/9b7c83...
>
> On Sep 7, 2:06 pm, Michael Pedersen <[email protected]> wrote:
>

-- 
You received this message because you are subscribed to the Google Groups 
"TurboGears" 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/turbogears?hl=en.

Reply via email to