#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
VARCHAR2andLOBcolumns which containJSON(and have theIS JSONcheck constraint enabled) in the same way as columns of typeJSON(which requires Oracle Database 21c or higher) are fetched. In thick mode this requires Oracle Client 19c or higher. The attributeoracledb.__future__.old_json_col_as_objmust 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 , 11 months ago
| Cc: | added |
|---|---|
| Keywords: | oracle python-oracledb added |
comment:2 by , 11 months ago
| Has patch: | set |
|---|
comment:3 by , 11 months ago
| Triage Stage: | Unreviewed → Accepted |
|---|
Note:
See TracTickets
for help on using tickets.
PR