Re: cx_Oracle 5.2 - more issues, new user

On 30/07/2015 7:44 am, Mike Bayer wrote:
>
>
> On 7/28/15 11:33 PM, Christopher Jones wrote:
>>
>> Is it still an issue?  I can see comments "That did it" and "Glad it
>> worked out" in the SQLAlchemy thread - was that a resolution with 5.2
>> or from reverting to 5.1.3?
>>
>> If it's still an issue, then post a currently reproducible test case &
>> the SQL to create the schema.  Knowing Oracle client library & DB
>> version numbers, as well as platform and environment settings,
>> including NLS values would help.
> So the issue is that cx_Oracle 5.2 added a type called "UNICODE", which we specifically looked for it being absent in order to detect whether or not
> the library is using "unicode mode", which is a legacy py2K mode introduced in early cx_Oracle 5 versions.   Because 5.2 adds this, we'd get the
> impression we were *not* in unicode mode and we'd not correctly set our "convert unicode" flags for py3K. All the b'' strings we see in these logs are
> *incorrect* - SQLAlchemy should be sending these as Python unicode objects, and that's what we did for 5.1.3.
>
> So issue resolved, thanks for all the help !


Thanks for the clarification.

Chris

-- 
http://twitter.com/ghrd

------------------------------------------------------------------------------