Opened 6 months ago

Closed 6 months ago

Last modified 6 months ago

#35054 closed Bug (fixed)

Add support for oracledb 2.0.

Reported by: Mariusz Felisiak Owned by: Mariusz Felisiak
Component: Database layer (models, ORM) Version: 5.0
Severity: Release blocker Keywords: oracle python-oracledb
Cc: Christopher Jones Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

The Oracle back-end doesn't work with ​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 ​Christopher's article.

Change History (5)

comment:1 by Mariusz Felisiak, 6 months ago

Cc: Christopher Jones added
Keywords: oracle python-oracledb added

comment:2 by Mariusz Felisiak, 6 months ago

Has patch: set

​PR

comment:3 by David Smith, 6 months ago

Triage Stage: Unreviewed → Accepted

comment:4 by GitHub <noreply@…>, 6 months ago

Resolution: → fixed
Status: assigned → closed

In 6c08dba:

Fixed #35054 -- Fixed crash on Oracle when fetching JSONFields with oracledb 2.0.0.

comment:5 by Mariusz Felisiak <felisiak.mariusz@…>, 6 months ago

In 42c31f86:

[5.0.x] Fixed #35054 -- Fixed crash on Oracle when fetching JSONFields with oracledb 2.0.0.

Backport of 6c08dba5176606e8a62dd108bb6c9467d678d2f4 from main

Note: See TracTickets for help on using tickets.
Back to Top