On Tue, Feb 18, 2014 at 4:08 PM, Michael Bayer mike...@zzzcomputing.com wrote:
OK some questions:
1. what options are you passing to create_engine()?
sqlalchemy.default.url = postgresql://DBNAME:DBPASS@DBADDRESS/DBNAME
sqlalchemy.default.client_encoding=utf8
sqlalchemy.default.pool_recycle =
On Feb 19, 2014, at 3:03 AM, Valentino Volonghi dialt...@adroll.com wrote:
4. is this error only under load ?
it may be the issue noted by Jeff in another email, or not.
Nah, this issue is all the time, with or without load and we applied
Jeff fix and so far, early to say as it's a
FWIW I'm seeing not reproducible UnicodeEncodeErrors in my production
systems, too. Alas only on ones with heavier load, and also with sqlalchemy
0.7.9.
On Wed, Feb 19, 2014 at 3:45 PM, Michael Bayer mike...@zzzcomputing.comwrote:
On Feb 19, 2014, at 3:03 AM, Valentino Volonghi
I got it, this is a regression due to #2880.
On Feb 19, 2014, at 10:15 AM, Robert Forkel xrotw...@googlemail.com wrote:
FWIW I'm seeing not reproducible UnicodeEncodeErrors in my production
systems, too. Alas only on ones with heavier load, and also with sqlalchemy
0.7.9.
On Wed, Feb
Hey guys,
we've moved recently to SQLAlchemy 0.9.2 from 0.7.9.
This move coincided with the introduction of UnicodeEncoreErrors in our
system. They appear to be happening at random and have no real way for us
to debug as we can't really reproduce them, except that they happen in our
system
On Tue, Feb 18, 2014 at 02:42:36PM -0800, Valentino Volonghi wrote:
Hey guys,
we've moved recently to SQLAlchemy 0.9.2 from 0.7.9.
This move coincided with the introduction of UnicodeEncoreErrors in our
system. They appear to be happening at random and have no real way for us
to debug
On Feb 18, 2014, at 5:42 PM, Valentino Volonghi dialt...@adroll.com wrote:
Hey guys,
we've moved recently to SQLAlchemy 0.9.2 from 0.7.9.
This move coincided with the introduction of UnicodeEncoreErrors in our
system. They appear to be happening at random and have no real way for us to
