Hello Ian, > 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'll try that ! I applied the trunk related changeset base.py. I'll prefer not to switch to the whole trunk if possible. > 1128 characters is a strange limit. Am I correct in guessing that > string is roughly 4000 bytes when encoded in utf-8? Yes and I read issue with the 4000 characters limit. > Does this problem occur when using the Django development web server? > Or only when using a production-quality web server? I can try to run the manage.py runserver with the DB oracle. > 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'll try this as well. > This is wholly unrelated, and I don't recommend using it unless you > need full-text search support. I guessed ;) Thanks a lot. I'll send an update when I can test. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
