Re: ORM, Oracle and UTF-8 encoding problem.

On Wed, Jan 9, 2013 at 11:40 PM, Jani Tiainen <redetin@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?

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.