#24919: Add an option not to run migrations when running tests
-----------------------------+---------------------------------------------
Reporter: kairichard | Owner: andrewgodwin
Type: New feature | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: 1.9 | Triage Stage: Ready for checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+---------------------------------------------
Comment (by MarkusH):
Replying to [comment:11 timgraham]:
> Added some ideas for improvement to the PR.
>
> As I mentioned in IRC, it could also be useful to allow the
`DATABASES['TEST']['MIGRATE'] = False` option that Andrew's first PR
suggested to be a shortcut for setting `MIGRATION_MODULES = {'a': None,
'b': None', ...}` for all apps. This could be done later or in a separate
commit though. The main concern I have with this idea is whether or not it
makes sense in a multi-db situation.
I created #25388 to keep track of this proposal if somebody wants to work
on it.
--
Ticket URL: <https://code.djangoproject.com/ticket/24919#comment:15>
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/068.b9750b318d8112ac3736f719c0e8334a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
