#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 ubernostrum):
The argument you're making, essentially, is "this third-party library has
a useful, document, publicly-expoed feature, but nobody's allowed to use
it because SQLAlchemy has a bug". That is not a Django problem. That is
either SQLAlchemy's problem (they should be able to compatibly use
psycopg, which has a publicly-documented interface) or psycopg's problem
(they should not allow features used by one application to affect
another). I encourage you to lobby both of those projects to help out with
this, but Django should not refuse to use a useful, documented, publicly-
exposed feature of psycopg for the reasons you've given here.
--
Ticket URL: <http://code.djangoproject.com/ticket/5171#comment:6>
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
-~----------~----~----~----~------~----~------~--~---
