#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 timgraham):
Is this sentence from the 1.8 release notes applicable?
An app without migrations with a ForeignKey to an app with migrations may
now result in a foreign key constraint error when migrating the database
or running tests. In Django 1.7, this could fail silently and result in a
missing constraint. To resolve the error, add migrations to the app
without them.
If not, we'll need a sample project that we can use to reproduce and debug
the issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/25238#comment:3>
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.5ad33b32a9a17438edf2806fca96be9c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
