#25930: Django-migrations & sqlite3 fail when migration-history is non-linear
-------------------------------+--------------------------------------
Reporter: vanschelven | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version:
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
-------------------------------+--------------------------------------
Changes (by charettes):
* needs_better_patch: => 0
* version: 1.8 =>
* needs_tests: => 0
* needs_docs: => 0
Comment:
Hi @vanschelven,
Thanks to your very detailed report I managed
[https://github.com/charettes/django-
ticketing/commit/621c8ca210b3253af12da4ae77c8ae19e8d5086f to reproduce]
against the latest Django 1.7.
The good news is that while I didn't bisect the exact commit but the issue
seems to be fixed on Django 1.8 which is the oldest supported version at
this point.
Please confirm 1.8 solves your reported issue. If it does please resolve
this ticket as invalid as Django 1.7 is not supported anymore.
--
Ticket URL: <https://code.djangoproject.com/ticket/25930#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.cd2946c28876e42043d66edd3fbe4b69%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
