#36189: Oracle Backend with `"use_returning_into": False` Option Fails to
Retrieve
Last Inserted ID
-------------------------------------+-------------------------------------
Reporter: ybjeon01 | Owner: Amaan-
| ali03
Type: Bug | Status: assigned
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Amaan-ali03):
* cc: Amaan-ali03 (added)
* easy: 1 => 0
* owner: (none) => Amaan-ali03
* status: new => assigned
Comment:
"Hey Django Team,
I’d love to work on this issue! From what I understand, the problem comes
from the last_insert_id() method in oracle/operations.py, where the query
fails when "use_returning_into": False is set.
Plan to Fix:
Reproduce the issue in django-docker-box with Oracle.
Update the query to correctly fetch currval, as proposed.
Add tests to ensure the fix works with and without "use_returning_into".
Run the full Django test suite to confirm no regressions.
Could you assign this to me? Looking forward to contributing!
Thanks,
Amaan Ali
--
Ticket URL: <https://code.djangoproject.com/ticket/36189#comment:1>
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/0107019508f9e630-1989424b-315c-4ef0-939a-84463181d5b9-000000%40eu-central-1.amazonses.com.
