#5996: psycopg2 raises "can't adapt" error where other backends work happily
------------------------+---------------------------------------------------
Reporter: zgoda | Owner: anonymous
Status: assigned | Component: Database wrapper
Version: SVN | Resolution:
Keywords: | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------+---------------------------------------------------
Changes (by [EMAIL PROTECTED]):
* stage: Unreviewed => Accepted
Comment:
We have looked at the issue as part of the 01-dec sprint. The issue is
psycopg2 specific. Psycopg2 is indeed not able to adapt the SafeUnicode
field even though SafeUnicode is a subclass of unicode. We are thinking
about adding a psycopg adapter for the SafeUnicode type in the psycopg2
backend as proposed here:
http://www.initd.org/tracker/psycopg/wiki/psycopg2_documentation
#adaptation-of-python-values-to-sql-types
Unit tests + patch will be added soon
--
Ticket URL: <http://code.djangoproject.com/ticket/5996#comment:5>
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
-~----------~----~----~----~------~----~------~--~---
