On Saturday, September 19, 2015 at 8:14:31 AM UTC-7, Michael Bayer wrote:
>
>
>
> On 9/18/15 7:58 PM, George Reilly wrote:
>
>
> Thanks for the prompt answer. I tried after_cursor_execute, but it didn't
> really help as I just got a tuple of the values, without a clear way to
> associate them
On 9/18/15 7:58 PM, George Reilly wrote:
Thanks for the prompt answer. I tried after_cursor_execute, but it
didn't really help as I just got a tuple of the values, without a
clear way to associate them with the parameter names. Ultimately, I
found that the following gives me the best
I find [SQLTap](http://sqltap.inconshreveable.com/) invaluable for
profiling SQLAlchemy queries. Currently, I've reduced one operation in our
system from nearly 12,000 queries to 800, and I'm not finished yet.
SQLTap listens for the before_execute and after_execute events. In
after_execute, it
On Fri, Sep 18, 2015 at 1:33 PM, Mike Bayer
wrote:
>
> On 9/18/15 3:22 PM, George Reilly wrote:
>
> I find [SQLTap](http://sqltap.inconshreveable.com/) invaluable for
> profiling SQLAlchemy queries. Currently, I've reduced one operation in our
> system from nearly
On 9/18/15 3:22 PM, George Reilly wrote:
I find [SQLTap](http://sqltap.inconshreveable.com/) invaluable for
profiling SQLAlchemy queries. Currently, I've reduced one operation in
our system from nearly 12,000 queries to 800, and I'm not finished yet.
SQLTap listens for the before_execute