Anonymous wrote:

Ah, I forgot to add my e-mail address as cc: solipsis@pitrou.net. Sorry.

Anonymous wrote:

Sorry again :) It's solipsis at pitrou dot net.

Michael Bayer (@zzzeek) wrote:

Arbitrarily/implicitly truncating a generated SQL statement in the log sounds awfully unreasonable to me. I'm looking at a SQL statement right in my terminal right now that's 3195 characters, and I need every single one of them to paste into my command line tool for testing.

This use case can be handled easily within the Python logging module itself using a custom handler so for the moment I'm -1 on this as a SQLAlchemy behavior and -10 as an automatic behavior. Will forward to the development list for alternative suggestions.

Changes by Michael Bayer (@zzzeek):

• changed title from "logging should be reasonable" to "arbitrarily truncate SQL log messages ? allow som"
• set milestone to "0.7.xx"

Michael Bayer (@zzzeek) wrote:

Oh, you're talking about the parameter lists? That's a different story. We do truncate those in exception messages already. Can you please add some specifics here as I am open to the latter and not the former.

Anonymous wrote:

Yes, I mean the parameter lists :)
For example executing conn.execute(sometable.insert(), some_huge_list_of_dicts).

Michael Bayer (@zzzeek) wrote:

patch is attached some tests would be nice, for both exception throw (surprised we don't have that) as well as log output

Changes by Michael Bayer (@zzzeek):

• changed milestone from "0.7.xx" to "0.7.3"

Michael Bayer (@zzzeek) wrote:

d3c1f24

Changes by Michael Bayer (@zzzeek):

• changed status to closed