#34320: Renaming fields with truncated names don't remove old constraints on
Oracle.
-------------------------------------+-------------------------------------
Reporter: Georgi Yanchev | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: oracle | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* keywords: => oracle
* stage: Unreviewed => Accepted
Comment:
Thanks for the report. As far as I'm aware, the main reason is that
`BaseDatabaseSchemaEditor._constraint_names()`
[https://github.com/django/django/blob/69069a443a906dd4060a8047e683657d40b4c383/django/db/backends/base/schema.py#L1748-L1765
doesn't use] truncated column names.
--
Ticket URL: <https://code.djangoproject.com/ticket/34320#comment:3>
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/0107018631aca67e-b460bcf7-590b-4333-90b6-8b99b2cc5175-000000%40eu-central-1.amazonses.com.
