Hello, Andrew All of our Tag, Startup, NewsLink, and Post will be right back in the database thanks to our data migrations. Example 22.40
Why? a) you dumped the whole database, and b) you only did makemigrations for the User app. we opt to remove the CreateModel operation for Profile and move it into its own migration file. Example 22.39 I followed your example, but got this error *CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0002_profile, 0001_user in account). To fix them run 'python manage.py makemigrations –merge'* What happened here? The only obvious difference between your examples and mine is the Python version, and I don't see how that's relevant here. It seems to be purely a Django migrations thing. thx -- 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 [email protected]. To post to this group, send email to [email protected]. 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/41d9d43e-84a8-4233-a8c6-faa7d9d42c44%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
