10.1.2013 8:59, Ian Kelly kirjoitti:
On Wed, Jan 9, 2013 at 11:40 PM, Jani Tiainen <rede...@gmail.com> wrote:
If we just force using force_unicode everything works except in older
versions of cx_Oracle (our server had 5.0.4 or something) connection strings
can't be unicode for some reason.
Sure, that's why the check exists in the first place. Prior to 5.1
cx_Oracle could be built either with Unicode or without. If the
former, it would accept only unicode strings and would raise an
exception on byte strings. If the latter, it would be exactly the
opposite.
Does it work for you using force_bytes with 5.0.4?
That's on my production server that runs 1.3.x version. smart_str (which
detection selects) does not work.
using force_unicode works (except for connection string).
Also depending on what OCI client 10.2.0.5 or instant client 11.2 is
used when compiling cx_Oracle causes variation. 10.2.0.5 doesn't work
with smart_str while 11.2 does work.
Both can take plain unicode (u'<some unicode stuff here>') when using
just cx_Oracle commands without any problems.
Note:
If I add manually some unicode to database Django can read it without
any problems.
--
Jani Tiainen
- Well planned is half done and a half done has been sufficient before...
--
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.
