id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
11706	Use of RETURNING should be optional	Matt Boersma	nobody	"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.""

 at least in version 9isupported only in Oracle 10g and later, so effectively Django 1.1 will no longer work on Oracle 9i because INSERT statements will fail with ""ORA-22816: unsupported feature with RETURNING clause.
}}}

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."		new	Database layer (models, ORM)	1.1			Oracle oracle RETURNING	Erin Kelly	Accepted	0	0	0	0	0	0