#9935: The session db backend throws UnicodeEncodeError when used with Oracle
----------------------------------------------+-----------------------------
Reporter: jamesli | Owner: nobody
Status: new | Milestone: post-1.0
Component: django.contrib.sessions | Version: 1.0
Resolution: | Keywords: oracle session
unicode UnicodeEncodeError
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------------+-----------------------------
Comment (by ikelly):
What version of cx_Oracle is being used in these setups? My hope is that
this is occurring with cx_Oracle 5.0, in which case the solution is easy:
don't use that. cx_Oracle 5.0 has a known NCLOB decoding bug that makes
it unusable for Django (I suppose we should document this). cx_Oracle
trunk and the upcoming 5.0.1 release should be okay, as is the 4.4.1
release.
If you're not using cx_Oracle 5.0, let me know so we can investigate
further.
--
Ticket URL: <http://code.djangoproject.com/ticket/9935#comment:4>
Django <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 django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
