we use the warnings filter to turn warnings into exceptions, either from the Python command line or programatically:
https://docs.python.org/2/library/warnings.html https://docs.python.org/2/using/cmdline.html#cmdoption-W On 7/2/14, 3:26 AM, Hans-Peter Jansen wrote: > Dear SQLAchemistas, > > this is an issue, that my apps choke on from time to time, _related_ to SQLA. > > Although, logging is set up correctly, some operations spit out senseless > warning messages like this: > > /usr/lib/python2.6/site-packages/sqlalchemy/engine/default.py:324: Warning: > Data truncated for column 'sendungref1' at row 1 > cursor.execute(statement, parameters) > > FYI, this is the solely message, catched by cron, from code that is exercised > heavily. > > Sure, I understand, that with some probability, this is triggered from MySql- > python-1.2.3 under the covers, and I know, that the value given for this > column was too big, but without any context, it doesn't help in any way. > > So strictly speaking, I'm barking up the wrong tree, but the question is, > have > you figured out a way to either catch or suppress those warnings? Is there a > mysql adapter, that cooperates better in this respect? > > Thanks for your insights, > > Pete > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
