Re: Django 1.1, cx_oracle 5.0.2, Oracle 9i, NCLOB Textfield

2009-10-01 Thread alphacc
Ok if you change the NCLOB to CLOB in the django\db\backends\oracle \creation.py and re-run a clear syncdb it works. Now what are the limitation of CLOB vs NCLOB ? Will it affect other part of the TextField methods ? --~--~-~--~~~---~--~~ You received this message b

Re: Django 1.1, cx_oracle 5.0.2, Oracle 9i, NCLOB Textfield

2009-10-01 Thread alphacc
I installed 9i at home and did some more test. With the same application running (and updating the same field) I discovered that the limit is not the same for my database. It is now 1246 Characters. I started a new application (a app with a model and a Textfield) and the limitation is 1316. I'll

Re: Django 1.1, cx_oracle 5.0.2, Oracle 9i, NCLOB Textfield

2009-10-01 Thread alphacc
> > 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 r

Re: Django 1.1, cx_oracle 5.0.2, Oracle 9i, NCLOB Textfield

2009-09-30 Thread alphacc
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