Re: [cx-oracle-users] cx_Oracle 5.2 - more issues, new user

[Mike B. <mi...@zz...>]

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 !





>
> Chris
>
> On 29/07/2015 4:11 am, Mike Bayer wrote:
>> OK, to continue this, I have *more* users reporting issues with
>> cx_Oracle 5.2 on Python 3 which disappear when they downgrade to 5.1.3.
>> At this point I am expecting many more user issues with cx_Oracle 5.2,
>> as whether it has something to do with build mis-matches or what, it is
>> either a mistake that is suddenly very easy to make by an end user,
>> something SQLAlchemy is doing which is suddenly not compatible with
>> cx_Oracle 5.2, or a bug in cx_Oracle itself.
>>
>> For this user, he is receiving random "cannot insert NULL into <some
>> schema / table / column>" errors, where the column is different each
>> time.  Log output of SQL emitted again shows it emitted as bytestrings
>> and the values are definitely present.
>>
>> This user's log output can be seen in the thread at
>> https://groups.google.com/forum/#!topic/sqlalchemy/OTwV1GZwgQo.
>>
>> Again, if a cx_Oracle developer could come up with a concrete reason why
>> these different-seeming errors are suddenly appearing, that would be
>> helpful.
>>
>>
>>
>> On 7/23/15 9:43 PM, Mike Bayer wrote:
>>>
>>> On 7/23/15 4:06 PM, Shai Berger wrote:
>>>> On Thursday 23 July 2015 04:13:20 Mike Bayer wrote:
>>>>> https://bitbucket.org/zzzeek/sqlalchemy/issues/3491/queryfirst-sometimes-returns-none 
>>>>>
>>>>>
>>>> The user is running on Windows with Oracle  11.1 client. The first 
>>>> question
>>>> that comes to mind is, did they compile cx_Oracle themselves? If not,
>>>> perhaps the issue is caused by running a cx_Oracle compiled against
>>>> Oracle 11.2 client libs, against a 11.1 client installation?
>>>>
>>>> AFAIK you can no longer download 11.1 from Oracle, that version
>>>> has been EOL'd I think.
>>> great catch!   I've asked the user for more information, but if I don't
>>> get a response I'll likely close the issue based on lack of 
>>> information.
>>>
>>>
>>>
>>>
>>>> Shai.
>>>>
>>>> ------------------------------------------------------------------------------ 
>>>>
>>>> _______________________________________________
>>>> cx-oracle-users mailing list
>>>> cx-...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/cx-oracle-users
>>>
>>> ------------------------------------------------------------------------------ 
>>>
>>> _______________________________________________
>>> cx-oracle-users mailing list
>>> cx-...@li...
>>> https://lists.sourceforge.net/lists/listinfo/cx-oracle-users
>>
>>
>> ------------------------------------------------------------------------------ 
>>
>> _______________________________________________
>> cx-oracle-users mailing list
>> cx-...@li...
>> https://lists.sourceforge.net/lists/listinfo/cx-oracle-users
>>
>