#29444: Allow fields to be part of the RETURNING clause during INSERT
-------------------------------------+-------------------------------------
Reporter: Johannes Hoppe | Owner: Johannes
Type: | Hoppe
Cleanup/optimization | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: django, db, | Triage Stage: Accepted
returning, default, model, field |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* has_patch: 1 => 0
* stage: Ready for checkin => Accepted
Comment:
This ticket is doable on Oracle with `cx_Oracle` 6.3+ (see
[https://blogs.oracle.com/opal/python-cx_oracle-63-supports-dml-returning-
for-batch-statement-execution cx_oracle-63-supports-dml-returning-for-
batch-statement]) that's why I'm leaving it open. First attempt of fixing
this on Oracle was a part of the original PR (see
[https://code.djangoproject.com/attachment/ticket/29444/refs-29444-oracle-
part.diff a diff]).
--
Ticket URL: <https://code.djangoproject.com/ticket/29444#comment:24>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/067.a2af11e816f12b8e07d65d0985015b7b%40djangoproject.com.
