#29717: Provide a way for tests to run on an existing empty DB
-------------------------------------+-------------------------------------
Reporter: Curtis Maloney | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Curtis Maloney):
To clarify...
Basically, I want to separate create/drop of the DB with create/drop of
the objects within the DB, where currently we conflate the concepts.
Currently we have "must create db" vs. "may reuse db"
So we allow "must create db" which implies "must start clean"
We can do "may reuse db", but that currently forces "may reuse objects".
I'm trying to enable "may reuse db" with "must start clean".
--
Ticket URL: <https://code.djangoproject.com/ticket/29717#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 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/066.c51579cd3270bedb1e25e58cd4145cda%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
