#10473 closed (fixed)
Add support for "RETURNING" to Oracle backend.
Reported by: | Erin Kelly | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | dev |
Severity: | Keywords: | oracle returning | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
We should take advantage of the framework's new support for "RETURNING" clauses.
Change History (4)
comment:1 by , 16 years ago
milestone: | 1.1 → 1.1 beta |
---|
comment:2 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 15 years ago
Unfortunately, this is only supported in Oracle 10g and later. In 9i (which our common employer happens to use still), it returns this error:
ORA-22816: unsupported feature with RETURNING clause
So we either need a workaround here, or should specify that only Oracle 10g and later are supported in Django 1.1.
Note:
See TracTickets
for help on using tickets.
(In [10044]) Fixed #10473: Added Oracle support for "RETURNING" ids from insert statements.