failure with unicode factoid

Bug #598379 reported by Siggi on 2010-06-25
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Stefano Rivera

Bug Description

I think this is best explained by example

09:43 <&Siggi> tibid: literal よし
09:43 < tibid> Siggi: 1: is ok
09:43 <&Siggi> tibid: よし
09:43 < tibid> Siggi: That didn't go down very well. Burp.

Related branches

Max Rabkin (max-rabkin) on 2010-06-28
tags: added: factoid unicode
Changed in ibid:
assignee: nobody → Stefano Rivera (stefanor)
importance: Undecided → Medium
milestone: none → 0.1.1
status: New → In Progress
Stefano Rivera (stefanor) wrote :

As I suspcted, the database is returning UTF-8 encoded binary strings rather than unicode. It's a bug in my SA0.6 branch

Changed in ibid:
milestone: 0.1.1 → 0.2.0
Stefano Rivera (stefanor) wrote :

Didn't quite get to the bottom of this.

sqlalchemy enables psycopg2.extensions.UNICODE, my ibid.db is UTF8, client connection is UTF8, etc, but I was still getting binary strings back from sqlalchemy. Making sqlalchemy decode them for me (with use_native_unicode=False did the trick)

Changed in ibid:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers