#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
------------------------------------------------+---------------------------
Changes (by mtredinnick):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm not really enthused about making a change like this. The conversion is
designed to be done by the database interface, which is what we are doing.
Moving it all into Django feels unnecessary and will be slower in a lot of
cases, too.
We ''might'' need to do this for handling binary data, but I'm hoping we
can avoid doing so. Doing it just for SQLAlchemy isn't a good reason at
the moment. SQLAlchemy should allow client encoding settings and trying to
pass non-ASCII UTF-8 data through a setting that is set to SQL_ASCII feels
very dangerous.
Going to think about it some more, but my immediate reaction is a strong
-1. It would be fixing the problem in the wrong location. The workaround
is for you to create your own database backend (copy the
postgresql_psycopg2 one) and make the changes locally.
--
Ticket URL: <http://code.djangoproject.com/ticket/5171#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
