#35054: Add support for oracledb 2.0.
-------------------------------------+-------------------------------------
Reporter: Mariusz | Owner: Mariusz Felisiak
Felisiak |
Type: Bug | Status: assigned
Component: Database | Version: 5.0
layer (models, ORM) |
Severity: Release | Keywords:
blocker |
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
The Oracle back-end doesn't work with [https://python-
oracledb.readthedocs.io/en/latest/release_notes.html#oracledb-2-0-0-december-2023
oracledb==2.0.0], because it changed converters for `JSONField` and now
returns `dict` instead of `str`:
> ''"Added support for fetching `VARCHAR2` and `LOB` columns which contain
`JSON` (and have the `IS JSON` check constraint enabled) in the same way
as columns of type `JSON` (which requires Oracle Database 21c or higher)
are fetched. In thick mode this requires Oracle Client 19c or higher. The
attribute `oracledb.__future__.old_json_col_as_obj` must be set to the
value True for this behavior to occur. In version 2.0 this will become the
normal behavior and setting this attribute will no longer be needed."''
Check out [https://cjones-oracle.medium.com/python-oracledb-2-0-has-
asyncio-support-2b913e40f9ca Christopher's article].
--
Ticket URL: <https://code.djangoproject.com/ticket/35054>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018c8ac5e4c2-dbda2f7a-7861-478a-8cf0-22dc13e6c026-000000%40eu-central-1.amazonses.com.
