> 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 critical bug 
fixes.  All progress will be under the new name.

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?

Regarding connection options, yes some things are supported with the Easy 
Connect Plus syntax.  There are some connection properties that aren't 
supported, e.g  application contexts (this was also true of cx_Oracle). And 
maybe more in future depending what users ask for. A generic way to set 
these, e.g with OPTIONS is a good direction.  

Chris

On Tuesday, May 31, 2022 at 7:04:07 PM UTC+10 Mariusz Felisiak wrote:

> 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 driver are additional connect() 
>>> keyword arguments like hostname, port, service_name, tcp_connect_timeout.  
>>> (The makedsn() function is now deprecated in python-oracle because of 
>>> this change.)  How can new parameters best be passed to python-oracledb?
>>>
>>
> As far as I'm aware this is already supported with an easy connect string 
> or full DSN in *NAME*, see docs 
> <https://docs.djangoproject.com/en/4.0/ref/databases/#full-dsn-and-easy-connect>
> .
>
> Best,
> Mariusz
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/6f449d19-8560-4f29-8eb9-61e5aea63b45n%40googlegroups.com.

Reply via email to