#26822: New migrations not applied on clone databases (sqlite) when using
--parallel and --keepdb option
-----------------------------------+------------------------------------
Reporter: romgar | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 1.9
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 romgar):
I have proposed a solution to fix this issue:
https://github.com/django/django/pull/6884
Tell me what you think about this cloned database deletion/creation, even
with `keepdb` option.
--
Ticket URL: <https://code.djangoproject.com/ticket/26822#comment:3>
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.75a95dc3d2ffe4e3c428d007cd7bb4be%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
