#25686: Database router without "allow_migrate" method raises exception
-------------------------------------+-------------------------------------
Reporter: jcugat | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: allow_migrate | Triage Stage: Ready for
| checkin
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:"c6da4b0c687e9a0d1661e9a310f703b30c4a0988" c6da4b0c]:
{{{
#!CommitTicketReference repository=""
revision="c6da4b0c687e9a0d1661e9a310f703b30c4a0988"
Refs #25686 -- Forwardported 1.8.7 release note.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25686#comment:6>
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/064.983e1b10ca09cda0d7b25ebec3b32743%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
