Use of RETURNING should be optional
|Reported by:||Matt Boersma||Owned by:||nobody|
|Component:||Database layer (models, ORM)||Version:||1.1|
|Severity:||Keywords:||Oracle oracle RETURNING|
|Cc:||Ian Kelly||Triage Stage:||Accepted|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Description (last modified by )
See closed ticket #10473. The "RETURNING...INTO" SQL construct is supported in Oracle versions 9i and later, but with some significant restrictions:
Oracle Error :: ORA-22816 unsupported feature with RETURNING clause Cause RETURNING clause is currently not supported for object type columns, LONG columns, remote tables, INSERT with subquery, and INSTEAD OF Triggers. Action Use separate select statement to get the values.
The use of RETURNING INTO isn't mandatory, so perhaps we could refactor it so a settings.py option turns it off. Our use case is an in-house application that has several INSTEAD OF triggers.
Change History (7)
comment:3 Changed 7 years ago by
|Summary:||Use of RETURNING means Oracle 9i is no longer supported → Use of RETURNING should be optional|