Use of RETURNING should be optional

[Matt Boersma]

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.

[Malcolm Tredinnick]

Agree that it would be nice to keep supporting 9i. Given that we already do some version-specific mods for Oracle (regex_lookup_*), it'd be nice to do the same thing for "RETURNING INTO".

[Russell Keith-Magee]

Not critical for 1.2

[Ian Kelly]

(In [14765]) Fixed #11706: Added an Oracle connection option to disable the use of RETURNING INTO in INSERT statements.

[Jacob]

Milestone 1.3 deleted