From 91b365ef67c82d790dc6021882d39f7aed960a2e Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Tue, 21 Jun 2022 09:09:41 +0200 Subject: [PATCH] [4.1.x] Fixed #33789 -- Doc'd changes in quoting table/column names on Oracle in Django 4.0. Thanks Paul in 't Hout for the report. Regression in 1f643c28b5f2b039c47155692844dbae1cb091cd. Backport of a0608c4b111555023c24ab7333a42ec53dca6b42 from main --- docs/releases/4.0.txt | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/releases/4.0.txt b/docs/releases/4.0.txt index 31e327eaf9..d64e74941c 100644 --- a/docs/releases/4.0.txt +++ b/docs/releases/4.0.txt @@ -492,6 +492,15 @@ some cases. consequence, any custom deletion logic in ``delete()`` handlers should be moved to ``form_valid()``, or a shared helper method, if required. +Table and column naming scheme changes on Oracle +------------------------------------------------ + +Django 4.0 inadvertently changed the table and column naming scheme on Oracle. +This causes errors for models and fields with names longer than 30 characters. +Unfortunately, renaming some Oracle tables and columns is required. Use the +upgrade script in :ticket:`33789 <33789#comment:15>` to generate ``RENAME`` +statements to change naming scheme. + Miscellaneous -------------