On Tuesday, June 7, 2022 at 7:36:38 PM UTC+10 f.apo...@gmail.com wrote:
> Hi Chris,
>
> On Tuesday, June 7, 2022 at 11:30:46 AM UTC+2 christopher@gmail.com
> wrote:
>
>> The question is how to add support cleanly so that both names are
>> supported in 4.1? Is there a preference? Particul
Hi Chris,
On Tuesday, June 7, 2022 at 11:30:46 AM UTC+2 christopher@gmail.com
wrote:
> The question is how to add support cleanly so that both names are
> supported in 4.1? Is there a preference? Particularly how can it be be
> done to reuse code without (temporary) duplication?
>
Good
> I agree with Florian, I'd prefer adding support for *python-oracledb* in
Django 4.1 and immediately deprecate using *cx_Oracle *(will be removed in
Django 5.0).
That sounds fair. The cx_Oracle namespace won't have any substantive
changes; maybe some new wheels for Python 3.11, and any critic
I agree with Florian, I'd prefer adding support for *python-oracledb* in
Django 4.1 and immediately deprecate using *cx_Oracle *(will be removed in
Django 5.0).
*3. Supporting some new connection parameters and using service names
>> instead of SIDs*
>>
>> One new feature of the python-oracledb
Hi Chris,
a thin client seems like great news to me :)
On Friday, May 27, 2022 at 3:05:51 PM UTC+2 christopher@gmail.com wrote:
> 1a. What about completely replacing cx_Oracle with python-oracledb
> (oracledb)? Python-oracledb is just a major release of cx_Oracle with a new
> name. We hav
