#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: adrian
Status: new | Component:
Database wrapper
Version: SVN | Resolution:
Keywords: | Stage:
Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------------------+---------------------------
Comment (by Chris Wagner <[EMAIL PROTECTED]>):
I'm not particularly concerned about having to workaround this problem,
myself. My concern is in leaving others vulnerable to this same,
ridiculously-difficult-to-track-down bug.
It's not just about being compatible with SQLAlchemy; it's about leaving
the runtime environment as clean as possible. Django shouldn't be making
global changes that will affect other, unrelated components. SQLAlchemy
seems to play nice, by avoiding such global changes.
I would actually blame psycopg2, but I doubt I'd get a positive response
from its developer(s). It would probably be a much more dramatic change
to fix psycopg2. I suspect Django already does manual encoding/decoding
for some of the other backends, already...
--
Ticket URL: <http://code.djangoproject.com/ticket/5171#comment:3>
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
-~----------~----~----~----~------~----~------~--~---
