#2514: [patch] psycopg2 backend doesn't properly save/load unicode strings
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: defect | Status: closed
Priority: normal | Milestone:
Component: Admin interface | Version:
Severity: normal | Resolution: wontfix
Keywords: |
-----------------------------------+----------------------------------------
Changes (by Victor Ng <[EMAIL PROTECTED]>):
* resolution: => wontfix
* status: reopened => closed
Comment:
This change won't be put in until Django gets full unicode support. For
now - either encode/decode to UTF8 when going to the database or call the
psycopg2.extensions.register_type function in your own code.
See the [http://groups.google.com/group/django-
developers/browse_thread/thread/4575a3fe0d78e2e4/d607d96f7b422620?#d607d96f7b422620
django-dev thread] for more details.
--
Ticket URL: <http://code.djangoproject.com/ticket/2514>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
