mirror of
https://github.com/django/django.git
synced 2025-08-04 10:59:45 +00:00
Fixed #11706: Added an Oracle connection option to disable the use of RETURNING INTO in INSERT statements.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@14765 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
dceaa82dec
commit
1f68dc4ad4
2 changed files with 23 additions and 1 deletions
|
@ -585,6 +585,23 @@ your Oracle database configuration to True::
|
|||
|
||||
Failure to do this may result in crashes and other odd behavior.
|
||||
|
||||
INSERT ... RETURNING INTO
|
||||
-------------------------
|
||||
|
||||
By default, the Oracle backend uses a ``RETURNING INTO`` clause to efficiently
|
||||
retrieve the value of an ``AutoField`` when inserting new rows. This behavior
|
||||
may result in a ``DatabaseError`` in certain unusual setups, such as when
|
||||
inserting into a remote table, or into a view with an ``INSTEAD OF`` trigger.
|
||||
The ``RETURNING INTO`` clause can be disabled by setting the
|
||||
``use_returning_into`` option of the database configuration to False::
|
||||
|
||||
'OPTIONS': {
|
||||
'use_returning_into': False,
|
||||
},
|
||||
|
||||
In this case, the Oracle backend will use a separate ``SELECT`` query to
|
||||
retrieve AutoField values.
|
||||
|
||||
Tablespace options
|
||||
------------------
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue