#25686: Database router without "allow_migrate" method raises exception
-------------------------------------+-------------------------------------
Reporter: jcugat | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: allow_migrate | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by charettes):
* severity: Normal => Release blocker
* needs_better_patch: 0 => 1
* component: Uncategorized => Database layer (models, ORM)
* has_patch: 0 => 1
* type: Uncategorized => Bug
* stage: Unreviewed => Accepted
Comment:
Hi jcugat, thanks for spotting this issue.
Please rebase the patch on the `1.9.x` branch (which also have this issue)
and add a release note for the upcoming 1.8.x release. Commiters will take
care of the backporting to 1.8.x and the release note forward porting to
master. I guess a simple regression test wouldn't hurt here.
--
Ticket URL: <https://code.djangoproject.com/ticket/25686#comment:2>
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.fae497d5c9f44539deed4a6b6037c1a0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
