Well, I had a dream. In this dream I could write something like
sqlalchemy.default.autoexplain = True
in my pylons config and it caused all my select and update statements
being executed with (here it is Postgres backend)
EXPLAIN ANALYZE SELECT col1, col2 FROM ...
Why bother? Well, it would make it perfect tool to easily verify
execution plans while developing. Current alternative (copy SQL
printed thanks to sqlalchemy.default.echo and issue EXPLAINs manually)
is tedious, especially considering one must substitute all the
params....
Is there any place in sqlalchemy where such a thing could be injected
without too much hassle?
PS Explain functionality is of course non-standard and different in
every database, but ... most databases do it in a way or another.
--
----------------------------------------------------------------------
| Marcin Kasperski | Working overtime sucks the spirit and
| http://mekk.waw.pl | motivation out of a team. (Wells)
| |
----------------------------------------------------------------------
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
