#24729: Test --keepdb option is incompatible with data migrations.
-------------------------------------+-------------------------------------
Reporter: acoady | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by acoady):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Old description:
> In 1.8 only, the test db is flushed before running migrations. But when
> using --keepdb the migrations won't be run, therefore any app which has
> data migrations will effectively be broken. For most non-trivial apps,
> their test setups won't even run.
>
> In 1.9, this issue is already handled because the flushing the test db
> has been removed anyway.
New description:
In 1.8 only, the test db is flushed before running migrations. But when
using --keepdb the migrations won't be run, therefore any app which has
data migrations will effectively be broken. For most non-trivial apps,
their test setups won't even run.
In 1.9, this issue is already handled because flushing the test db has
been removed anyway.
https://github.com/django/django/pull/4582
--
--
Ticket URL: <https://code.djangoproject.com/ticket/24729#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/064.1d612431e8c5d17c79c336fe4f88aaa5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
