#24742: Can't runserver on a read-only database due to migrations
-----------------------------+------------------------------------
Reporter: delgiudices | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Comment (by shaib):
A workaround could be to add a router that directs all models from the
"migrations" app into some sqlite database (in fact, if it works, it could
be packed up nicely as a solution).
However, indeed, such a solution flies in the face of #24699, which
essentially asks for a migration table in each db.
--
Ticket URL: <https://code.djangoproject.com/ticket/24742#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/069.614e743fe22cd5a0fe17909bf690348e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
