#5171: postgresql_psycopg2 backend registers psycopg2's UNICODE extension, which
can cause interference if Django is not the only component using psycopg2
------------------------------------------------+---------------------------
Reporter: Chris Wagner <[EMAIL PROTECTED]> | Owner: nobody
Status: new | Component:
Database wrapper
Version: SVN | Resolution:
Keywords: | Stage: Design
decision needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------------------+---------------------------
Comment (by jacob):
FWIW, {{{connection.set_client_encoding('utf8')}}} is syntaxtic sugar for
executing the SQL statement {{{SET client_encoding = 'utf8'}}}. So you
should be able to just run that SQL directly against SQLAlchemy (if it's
preventing you from running that particular statement, then that really
''is'' a bug).
I'm not sure weather Django ought to change anything here... I'll have to
think about the ramifications a bit more.
--
Ticket URL: <http://code.djangoproject.com/ticket/5171#comment:8>
Django Code <http://code.djangoproject.com/>
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?hl=en
-~----------~----~----~----~------~----~------~--~---
