#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
-----------------------------+------------------------------------
Changes (by aaugustin):
* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
This is a valid use case, there should be a way to support it.
This is somewhat related to #24669.
--
Ticket URL: <https://code.djangoproject.com/ticket/24742#comment:1>
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.93d5934d928b63d96e278bba3c704ae8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
