failure with unicode factoid

Bug #598379 reported by Siggi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ibid
Fix Committed
Medium
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)
tags: added: factoid unicode
Changed in ibid:
assignee: nobody → Stefano Rivera (stefanor)
importance: Undecided → Medium
milestone: none → 0.1.1
status: New → In Progress
Revision history for this message
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
Revision history for this message
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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.