#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: Design
decision needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------------------+---------------------------
Changes (by mtredinnick):
* stage: Unreviewed => Design decision needed
Comment:
This is either a psycopg2 bug (because it doesn't do encoding
transformations on a per-connection basis) or an SQLAlchemy bug (because
it imposes expectations on the connection encoding without controlling it
itself or bothering to discover what it might be) or both. Django takes
explicit responsibility for the connection encoding. We work out what it
is, we adapt. Moving all the manual encoding/decoding into Django is
slower and more maintenance and we're using the database interface
correctly, so it's a really ugly solution to somebody else's problem.
Still, we might have to work around other broken software because they're,
well, broken. I'm still thinking about this.
--
Ticket URL: <http://code.djangoproject.com/ticket/5171#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
