#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: Simon Charette (added)
Comment:
> I agree with you. Another case I can think of (although I haven't tested
it yet, so please correct me if I'm wrong, as this is based on my limited
experience) is when a user explicitly provides a value for the primary key
while creating an object, instead of relying on the nextval from the
sequence.
Right this is what is causing many test failures as described in comment:3
and why the solution is not appropriate as don't use `GENERATED ALWAYS`
which would disallow explicit assignment of primary key values.
> Another case that shows sequence is tied to transactions:
Thanks so at least this feature is not completely broken. I had not tried
it it out myself but I read mixed reports online depending on the
isolation level used (e.g. `READ COMMITTED` vs `REPEATABLE READ`).
--
Ticket URL: <https://code.djangoproject.com/ticket/36189#comment:6>
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/010701951a42da6a-98c85ca7-5d04-4eed-b17d-bd740508a480-000000%40eu-central-1.amazonses.com.
