#25896: SeparateDatabaseAndState.database_backwards() applies state incorrectly ----------------------------+------------------------------------ Reporter: amosonn | Owner: amosonn Type: Bug | Status: closed Component: Migrations | Version: 1.8 Severity: Normal | Resolution: fixed Keywords: | Triage Stage: Accepted Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 1 Easy pickings: 0 | UI/UX: 0 ----------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>): In [changeset:"0772bffd4a2feac3928924a8427f372ab3ec6919" 0772bffd]: {{{ #!CommitTicketReference repository="" revision="0772bffd4a2feac3928924a8427f372ab3ec6919" [1.8.x] Fixed #25896 -- Fixed state bug in SeparateDatabaseAndState.database_backwards(). Backport of 542b7f6c50df18f2aa201cf1de81577c1bee643c from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/25896#comment:4> 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.4f802d7c9df72d7656fd93c1f0e06441%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.