So the Pyramid debug toolbar system catches the before_cursor_execute to set up a timing start, and after_cursor_execute to calculate the duration. It's decent support for approximated query timing.
It didn't log any of the other events though, so I'm working on a solution to log them. The timing isn't important, but for my debugging needs I needed to catch them. Unlike default pyramid, I use multiple transactions -- so the lack of not knowing where a commit/rollback occurred makes the existing tool of very limited use to me. -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
