#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):
I am no expert in Django but I was just wondering if it is possible to
change how Django handle migration with existing tables.
{{{
Run python manage.py migrate. Django will see that the tables for the
initial migrations already exist and mark them as applied without running
them.
}}}
The above is taken from Django documentation. Instead of marking them as
applied unconditionally, it would be really helpful if Django could throw
out some sort of error if the existing database structure doesn't match
model.py (via inspectdb?).
--
Ticket URL: <https://code.djangoproject.com/ticket/24178#comment:3>
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.dd6cac39e300fa764cf458f4c976c779%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
