#24067: Renaming models prompts for content type deletions
-------------------------------------+-------------------------------------
Reporter: doepunk | Owner: charettes
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: | 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 Simon Charette <charette.s@…>):
In [changeset:"722344ee59fb89ea2cd5b906d61b35f76579de4e" 722344ee]:
{{{
#!CommitTicketReference repository=""
revision="722344ee59fb89ea2cd5b906d61b35f76579de4e"
Refs #24067 -- Fixed contenttypes rename tests failures on Oracle.
Broke the initial migration in two to work around #25530 and added
'django.contrib.auth' to the available_apps to make sure its tables are
also
flushed as Oracle doesn't implement cascade deletion in sql_flush().
Thanks Tim for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24067#comment:17>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.c79e7a215c9c038065a5f502fc52aa97%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
