summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorKevin Grinberg <kevin@activefrequency.com>2017-08-22 17:41:25 -0400
committerTim Graham <timograham@gmail.com>2017-08-22 17:41:25 -0400
commit90be8cf2a4d81005c5c35074ba763f5fd3a56bd1 (patch)
tree0fc58c059ac1a729ed089a776c3b3243523cce5e /docs
parent60f81118f412268f317abbcc7509e315a714315d (diff)
[1.11.x] Fixed #28451 -- Restored pre-Django 1.11 Oracle sequence/trigger naming.
Regression in 69b7d4b116e3b70b250c77829e11038d5d55c2a8. Backport of c6a3546093bebae8225a2c5b7e0836a2b0617ee5 from master
Diffstat (limited to 'docs')
-rw-r--r--docs/releases/1.11.5.txt8
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/releases/1.11.5.txt b/docs/releases/1.11.5.txt
index e7c6c91a5d..5cd38e3b98 100644
--- a/docs/releases/1.11.5.txt
+++ b/docs/releases/1.11.5.txt
@@ -15,3 +15,11 @@ Bugfixes
* Fixed test database creation with ``cx_Oracle`` 6 (:ticket:`28498`).
* Fixed select widget rendering when option values are tuples (:ticket:`28502`).
+
+* Django 1.11 inadvertently changed the sequence and trigger naming scheme on
+ Oracle. This causes errors on INSERTs for some tables if
+ ``'use_returning_into': False`` is in the ``OPTIONS`` part of ``DATABASES``.
+ The pre-11.1 naming scheme is now restored. Unfortunately, it necessarily
+ requires an update to Oracle tables created with Django 1.11.[1-4]. Use the
+ upgrade script in :ticket:`28451` comment 8 to update sequence and trigger
+ names to use the pre-1.11 naming scheme