Re: Python 2: unicode vs str param causing slowness

Shai Berger <shai-9mtU2oJkgntWk0Htik3J/[email protected]> Thu, 22 Jan 2015 01:11:04 +0200
Newsgroups gmane.comp.python.db.cx-oracle
Organization Platonix Joint Ventures
Message-ID <[email protected]>
Hi Dayton,

On Tuesday 20 January 2015 17:55:46 Dayton Gomez wrote:
> Another interesting fact is that the slowness happens on 11g, but not
> oracle 12c. 12c seems to operate just fine with either. Both have:
> NLS_CHARACTERSET        WE8MSWIN1252
> NLS_NCHAR_CHARACTERSET        AL16UTF16
> 
The Django documentation says that Django assumes a server encoding of UTF8; 
your use of UTF16 could create problems with values Django will think are fine 
but your server will think are too long.

Django also uses utf8 as the client-side encoding -- and that may (or may not) 
be related to the performance problem.

I recommend that, if this makes sense businesswise, you try to use a utf8 
encoding such as AL32UTF8.

HTH,
	Shai.

------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet