#36189: Oracle Backend with `"use_returning_into": False` Option Fails to
Retrieve
Last Inserted ID
-------------------------------------+-------------------------------------
Reporter: Yeongbae Jeon | Owner: Amaan-
| ali03
Type: Bug | Status: assigned
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* cc: Mariusz Felisiak (added)
* stage: Unreviewed => Accepted
Comment:
I can replicate the issue but we should agree on a solution before
proceeding here.
This relates to #11706 (which introduced `use_returning_into`) and #27789
which changed the way `last_insert_id` works.
I tried applying the proposed patch and there are many tests that fail
with it against (Oracle `23.5.0.24.07`) so I wonder if there is something
else at play here. Given `use_returning_into` has been untested since its
introduction 15 years ago and now appears to be broken in non trivial ways
I wonder if we should just simply remove support for it instead of trying
to resolve this issue.
Any thoughts on the current situation Mariusz?
--
Ticket URL: <https://code.djangoproject.com/ticket/36189#comment:2>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019511972fda-fb04902f-d5c3-42f7-9b13-0d0a0c0d0809-000000%40eu-central-1.amazonses.com.
