> > This sounds like a character set encoding problem. The first thing I > > would try, if possible, is to 1) recompile cx_Oracle with the > > WITH_UNICODE option enabled and 2) switch to Django trunk (Django 1.1 > > does not support this option). This allows Django to send unicode > > strings rather than encoded strings and usually solves these sorts of > > problems. Beware that this could break any other software using > > cx_Oracle on the system.
I did compile the cx_Oracle 5.0.2 and change the backend with the appropriate changeset. No luck. I tried to switch to the django trunk as well. > > Does this problem occur when using the Django development web server? > > Or only when using a production-quality web server? Yes it happens as well when I use the dev server. > > Finally, what happens if you replace "Database.CLOB" in line 364 of > > django/db/backends/oracle/base.py with "Database.NCLOB" or > > "Database.LONG_STRING"? I had no luck with these changes. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
