#34320: Renaming fields with truncated names don't remove old constraints on
Oracle.
-------------------------------------+-------------------------------------
Reporter: Georgi Yanchev | Owner: Mohamed
| Nabil Rady
Type: Bug | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: oracle | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"3b09f3555859495ca0d130712d240fb61493739e" 3b09f355]:
{{{
#!CommitTicketReference repository=""
revision="3b09f3555859495ca0d130712d240fb61493739e"
[4.2.x] Fixed #34320 -- Make sure constraints names are obtained from
truncated columns names.
Backport of 6bdc3c58b65eb32fd63cd41849f00a17a36b4473 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34320#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018655c769c1-2b818a35-39d8-47ad-aa26-61c7612ce47e-000000%40eu-central-1.amazonses.com.
