#10566: Support cx_Oracle compiled with WITH_UNICODE ------------------------------------------+--------------------------------- Reporter: ikelly | Owner: nobody Status: new | Milestone: Component: Database layer (models, ORM) | Version: SVN Keywords: oracle unicode | Stage: Unreviewed Has_patch: 0 | ------------------------------------------+--------------------------------- If cx_Oracle 5.0.1+ is compiled with the WITH_UNICODE option, then it expects unicode inputs and rejects str inputs. Currently the oracle backend only passes encoded strings and so won't work with this setup.
This is something we'll need to address eventually as Django moves to Python 3.0 support, but another use case may be when running Django together with other software in the same Apache instance, resulting in NLS_LANG confusion, as documented in this thread: http://groups.google.com/group/django- users/browse_thread/thread/fb812a572168bfc8?hl=en -- Ticket URL: <http://code.djangoproject.com/ticket/10566> 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 -~----------~----~----~----~------~----~------~--~---
