Re: Django Unleashed, custom user model

Waited as long as I thought I could to hear from you. So here's my result:

(cannon)malikarumi@Tetuoan2:~/Projects/cannon/jamf$ python manage.py makemigrations --merge

Traceback (most recent call last):

…

raise ValueError("Could not find common ancestor of %s" % migration_names)

ValueError: Could not find common ancestor of set([u'0002_profile', u'0001_user'])

(...so I re-merged them back into a single document...)

(cannon)malikarumi@Tetuoan2:~/Projects/cannon/jamf$ python manage.py makemigrations account
No changes detected in app 'account'
(cannon)malikarumi@Tetuoan2:~/Projects/cannon/jamf$ python manage.py migrate
Operations to perform:
  Apply all migrations: admin, account, contenttypes, auth, sessions
Running migrations:
  Rendering model states... DONE
  Applying account.0001_initial... OK
The following content types are stale and need to be deleted:

    auth | user

Any objects related to these content types by a foreign key will also
be deleted. Are you sure you want to delete these content types?
If you're unsure, answer 'no'.

    Type 'yes' to continue, or 'no' to cancel: no
(cannon)malikarumi@Tetuoan2:~/Projects/cannon/jamf$

I thought you should be aware of these differing results.

On Tuesday, July 5, 2016 at 6:49:01 PM UTC-7, Malik Rumi wrote:

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 django-users+unsubscribe@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/be050074-7844-47d8-8e24-03bb85e73053%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.