#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: closed | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: wontfix | Keywords:
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------------------+--------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => wontfix
Comment:
The SQLAlchemy ticket referenced in comment:7 has a workaround for
SQLAlchemy and some strong agreement that this is a psycopg2 bug. Closing
as wontfix for the reasons given in previous comments.
(Jacob, reopen if you have any really good ideas on a workaround, but I
don't see this as our problem at the moment; good citizenship works both
and SQLAlchemy have a workaround for the problem on their side.)
--
Ticket URL: <http://code.djangoproject.com/ticket/5171#comment:10>
Django <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
-~----------~----~----~----~------~----~------~--~---
