Calling loaddata in a migration will work until you modify the model's
fields. You can read more on Trac:
https://code.djangoproject.com/ticket/24778
On Thursday, December 1, 2016 at 12:09:49 PM UTC-5, Tom Evans wrote:
>
> Hi all
>
> We're moving a project over to the latest release (well, we're at 1.7
> now, but that's the end goal anyway) and replacing South migrations
> with Django migrations.
>
> It looks like that fixtures are no longer thought of as the correct
> way of providing initial data. Is this because Run{SQL,Python} can
> have "reverse" instructions included, or is it some other reason? I
> couldn't see anything pertinent in the docs.
>
> Given that we have an existing project and fixture files, is it very
> bad and wrong to simply have a data migration that runs loaddata on
> our required fixtures? It would not be reversible, but it would be
> massively simpler.
>
> Cheers
>
> Tom
>
--
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/d24855cb-4640-4cbd-849e-03d05058debe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
