#24178: Moving production data to a new database
-------------------------------+--------------------------------------
Reporter: liwee | Owner: nobody
Type: Uncategorized | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: needsinfo
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 liwee):
{{{
(Of course it would be nice to keep the auto-fake behavior AND verify that
the db state actually matches the models, as liwee suggested, but I don't
think that's practically feasible at all.)
}}}
I didn't mean for both to work at the same time.
1. For initial migration with existing tables, Django will first check if
db state match the model
2. if match, continue to auto-fake
3. if doesn't match, raise an error and auto-fake is aborted
User will adjust the db table manually and rerun initial migration again
--
Ticket URL: <https://code.djangoproject.com/ticket/24178#comment:6>
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/063.0fba0ff746e045fde87248f87501ee61%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
