El 24/04/15 12:16, Tim Graham escribió:
I don't think so. When you create your initial migrations, you need to
ensure they match the scheme of your database. After that, things
shouldn't get out of sync. Any idea how that happened in the first place?
On Friday, April 24, 2015 at 8:54:19 AM UTC-4, Андрей Лукьянов wrote:
Hi everyone. In my current project there is a great confusion of
migrations and it often ends up in an error when I try to apply
migrations because the fields the migrate tries to create are
already in the database. Is there any way for migrate to create
fields that are not in the database and skip those that are
already there? Sort of a partial migration. Now I have to edit
migration files manually commenting the fields that are already in
the database. Takes a lot of time for I can't compare the database
state and the state of migrations. So I have to do it field by
field...
it happens if you work on different copies of your project and delete
some migration files. That's what happened to me!
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/553A88EA.2020202%40epepm.cupet.cu.
For more options, visit https://groups.google.com/d/optout.
