#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:"826ec5ee57ba798f4706d4fd6f9ffa8b1065508d" 826ec5ee]: {{{ #!CommitTicketReference repository="" revision="826ec5ee57ba798f4706d4fd6f9ffa8b1065508d" [1.10.x] 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. Backport of 722344ee59fb89ea2cd5b906d61b35f76579de4e from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/24067#comment:18> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/065.cc2bd603e54fdccb3f0eb2b799fa14a8%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.