#23360: CircularDependencyError with AUTH_USER_MODEL set
-------------------------------+--------------------------------------
Reporter: brian | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.7-rc-3
Severity: Normal | Resolution:
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 brian):
Hello,
Splitting the migrate up does seem to have solved the problem. I deleted
the migrations, deleted the LogEntryWithGroup model, created the
migrations, added the LogEntryWithGroup model, created the migration. It
seems to work.
I think there might be rare cases where it is required to tweak the
automatically generated migrations like this.
Another case might be where you have two tables that have ForeignKeys to
each other in different Apps. Yes, I have seen this. Might need to delete
one of the foreign keys, create the migrations, add the foreign key back,
and create a new migration. So it is clear what order things need to be
created in.
Possibly this could be better documented.
In any case, if you want to close this ticket, I am happy with that.
Thanks
--
Ticket URL: <https://code.djangoproject.com/ticket/23360#comment:6>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.dc67598c4ccb0ba9ff1580dbf643d7c4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
