#25238: Django1.8 migrations, custom user model, in non-SQLite databases
-------------------------------------+-------------------------------------
Reporter: mallyvai | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
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 mallyvai):
Update - Did some more digging - it looks like the `registration` app is
causing the issue here. Commenting it out seemed to let it work.
It looks like upgrading django-registration-redux and django-registration
may have fixed the bug(!?!?!?) Forcing an update on it seemed to do the
trick. Will confirm before closing ticket.
For my own curiosity - how difficult might it be to add more verbose
logging to some of the migration/failure issues to indicate this specific
kind of failure case? Happy to try and submit a patch if it makes sense -
spent some time rooting around the migration/dependency loading classes so
can take a stab if it makes sense.
Cheers!
--
Ticket URL: <https://code.djangoproject.com/ticket/25238#comment:4>
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/066.a385aed24a624e397d66d65e1efea936%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
