#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:"fae76b81ce6d13245abc42752f0a82f16a9ba35f" fae76b81]:
{{{
#!CommitTicketReference repository=""
revision="fae76b81ce6d13245abc42752f0a82f16a9ba35f"
[4.2.x] Refs #34320 -- Added skipIf for a test requiring check
constraints.
Backport of 40e88ae8c899bcae3a9520f7a6519dd178185f85 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34320#comment:11>
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/01070186963a96d6-f7e65bc4-be47-49df-a732-974b936beaa5-000000%40eu-central-1.amazonses.com.
