Hi All,
So, we have some (well, about 1.7M a day, so more than some...) unknown
ROLLBACKs occurring. Creating the engine with echo=True can show use
that these rollbacks are indeed happening, but tracking these down lead
me to a more widespread question:
If you have analysis tools that tell you what SQL is getting executed
(such as MySQL's enterprise monitoring stuff) how can you track back a
SQL statement to the python code that caused it to be executed?
Is there some extension of or something to the ehco=True logging?
If not, how should I tackle this?
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
