Re: [Sqlalchemy-tickets] [sqlalchemy] #2837: Logging FAQ suggestion

[sqlalchemy <mi...@zz...>]

#2837: Logging FAQ suggestion
----------------------------------+------------------------------------
      Reporter:  jonathan         |      Owner:  zzzeek
          Type:  enhancement      |     Status:  new
      Priority:  lowest           |  Milestone:
     Component:  documentation    |   Severity:  no triage selected yet
    Resolution:                   |   Keywords:
Progress State:  awaiting triage  |
----------------------------------+------------------------------------

Comment (by jonathan):

 Limiting the size of these fields logging is a much better idea.

 It took me a while to dig out this general approach, and it seemed like a
 natural "need" by the current system... and also not in-line with the
 current docs.  ( I did not expect the logger path to be different like
 that, though it does make sense ).

 My dev box uses SqlAlchemy as the message broker for Celery Resizing (it's
 handled by Redis on Production ).  All of the sudden during some tests,
 I'm starting to see a 1.9MB jpeg converted into b64 and piped into an
 INSERT statement on sqlalchemy.  Not fun.

--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2837#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python