Re: [sqlalchemy] suppress echo of INSERT/UPDATE large binary data

On 08/17/2016 01:25 PM, Kent wrote: Generally, echo=True for log level of INFO is very helpful for log files. But on INSERT/UPDATE of a Binary column (at least with Oracle, BLOB) it sure would be nice to skip the logging of the sometimes massive binary data. Is this possible?

[sqlalchemy] Re: suppress echo of INSERT/UPDATE large binary data

On Wednesday, August 17, 2016 at 1:25:17 PM UTC-4, Kent wrote: > > Generally, echo=True for log level of INFO is very helpful for log files. > If you just have a few of these, you can wrap the flush: dbSession.add(bigObject) try: # wrap `flush` in a disabled block, so we don't go crazy

[sqlalchemy] suppress echo of INSERT/UPDATE large binary data

Generally, echo=True for log level of INFO is very helpful for log files. But on INSERT/UPDATE of a Binary column (at least with Oracle, BLOB) it sure would be nice to skip the logging of the sometimes massive binary data. Is this possible? Thanks, Kent -- You received this message because

[sqlalchemy] Re: Creating declared class in __declare_first__ causes RuntimeError: deque mutated during iteration

Figured it out. It wasn't FlaskSqlalchemy, it was me. The decalrative base class inherited from References which had the __declarefirst__ in it. Trying to instantiate a declarative class (which inherited from References) inside __declarefirst__ fired that event, which caused the error. I