#33177: Setting DATABASES[alias]["TEST"]["MIGRATE"] = False should mean that
`migrate` isn't run.
-----------------------------------+--------------------------------------
Reporter: Daniel Quinn | Owner: nobody
Type: New feature | Status: closed
Component: Testing framework | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Comment (by Daniel Quinn):
I'm not sure I understand the reasoning above, but if the project
considers this a wontfix, I'll find a way to roll with it.
Can I ask then, is there an officially sanctioned way to write a Django
project that talks to external, unmanaged databases that will also allow
you to write tests against local copies of those databases for integration
tests? I had thought that setting `MIGRATE=False` was it, but as it is,
simply having these databases in `settings.DATABASES` makes the test
runner write to them, which is really not awesome.
--
Ticket URL: <https://code.djangoproject.com/ticket/33177#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.b9e014230917ca1a4295201d2c502748%40djangoproject.com.
