#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):
This might be a very stupid idea ...
Assume the database already exist, say database name is mydb
Migration will
1. create another db called mydb_compare using model.py
2. export structure sql (no data) for mydb
3. export structure sql for mydb_compare
4. do a diff for these 2 files?
--
Ticket URL: <https://code.djangoproject.com/ticket/24178#comment:9>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.51b85b9eb4effd94f9b22b8496de170c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
