#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 timgraham):
The idea is that all changes to your database schema should have Django
migrations. If you are changing the schema in other ways, then you are on
your own.
--
Ticket URL: <https://code.djangoproject.com/ticket/24178#comment:4>
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.ad4872761acba3dc0f047f009b5f91db%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
