Erich Schubert wrote:
> DB is Postgresql; the issues didn't occur with sqlite3.
> I believe psycopg 1, not version 2. I don't know if this still is an
> issue with v2.
You're right - after replacing python-psycopg2 with python-psycopg
package I'm reproducing it.
I will report this to sqlalchemy's
Hi,
> I can't reproduce it (my query is always quoted). Could you provide an
> example code? What database are you using?
Example code - just use u"abc" somewhere, that should do the trick.
DB is Postgresql; the issues didn't occur with sqlite3.
I believe psycopg 1, not version 2. I don't know if
Erich Schubert wrote:
> I get data keys as unicode strings, albeit they only consist of regular
> characters. When I try to use them in sqlalchemy, broken SQL commands
> are generated. e.g.:
>
> SELECT count(foobar.foobarid) AS tbl_row_count
> FROM foobar
> WHERE foobar.foobarid = KiupZ8YqyzY
I c
Package: python-sqlalchemy
Version: 0.3.0-1
Severity: important
Tags: upstream
I get data keys as unicode strings, albeit they only consist of regular
characters. When I try to use them in sqlalchemy, broken SQL commands
are generated. e.g.:
SELECT count(foobar.foobarid) AS tbl_row_count
FROM foo
4 matches
Mail list logo
