I've had problems with this in the past. I thought it was SqlAlchemy, and
it ended up being issues with my data in Pyramid (the Pylons successor). A
few items had the wrong character encoding -- I was expecting it to be
UTF8/ASCII, but it was using a different charset.
It could be the issue
On Feb 18, 2014, at 5:42 PM, 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 as we
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 d
On Tuesday, February 18, 2014 2:42:36 PM UTC-8, Valentino Volonghi wrote:
>
> Can anyone help us figure out what this issue might be?
>
>
One last thing here is that our driver is psycopg 2.5.2
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To u
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 and
On Feb 18, 2014, at 2:06 PM, Christoph Zwerschke wrote:
> The docstring for the cx-Oracle dialog says:
>
> "SQLAlchemy will pass all unicode strings directly to cx_oracle, and
> additionally uses an output handler so that all string based result values
> are returned as unicode as well."
>
>
The docstring for the cx-Oracle dialog says:
"SQLAlchemy will pass all unicode strings directly to cx_oracle, and
additionally uses an output handler so that all string based result
values are returned as unicode as well."
The latter does no longer seem to be true; the handler was recently
r
On Feb 18, 2014, at 4:59 AM, Adrian wrote:
>
> Hi guys,
>
> After updating to 0.9.2 from 0.8 my custom compiles() are not working any
> longer. The definition looks likes this:
>
> @compiles(PrimaryKeyConstraint, "postgresql")
> def add_pg_primary_key_options(constraint, compiler, **kwargs):
Hi guys,
After updating to 0.9.2 from 0.8 my custom compiles() are not working any
longer. The definition looks likes this:
@compiles(PrimaryKeyConstraint, "postgresql")def
add_pg_primary_key_options(constraint, compiler, **kwargs):
ddl = compiler.visit_primary_key_constraint(constraint, *
