#24742: Can't runserver on a read-only database due to migrations
-----------------------------+---------------------------------------------
Reporter: delgiudices | Owner: nobody
Type: Bug | Status: closed
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
-----------------------------+---------------------------------------------
Changes (by Claude Paroz <claude@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"f61c4f490dc4c8ec6ba94ad4f40247db2425fc3e" f61c4f4]:
{{{
#!CommitTicketReference repository=""
revision="f61c4f490dc4c8ec6ba94ad4f40247db2425fc3e"
Fixed #24742 -- Made runserver.check_migrations ignore read-only databases
Thanks Luis Del Giudice for the report, and Aymeric Augustin and Markus
Holtermann for the reviews.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24742#comment:9>
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/069.adae9dc0447c77034caa6d368195b5da%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
