#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 GitHub <noreply@…>):
In [changeset:"fec4ed0a250841f41066cbbc9581993ba378d268" fec4ed0a]:
{{{
#!CommitTicketReference repository=""
revision="fec4ed0a250841f41066cbbc9581993ba378d268"
[4.2.x] Refs #34320 -- Skipped
SchemaTests.test_rename_field_with_check_to_truncated_name on MariaBD
10.5.2+.
This crashes since MariaDB was bumped to 10.5 on Jenkins.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34320#comment:13>
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/0107018ad6e929f8-7f700bc9-75fc-4915-bc33-61575eaa88d1-000000%40eu-central-1.amazonses.com.