Newer version of Sqlite (3.8.9) breaks django -- should we backport

[Peter J. Farrell]

Official ticket:

https://code.djangoproject.com/ticket/24637

PR:

https://github.com/django/django/pull/4494

Sqlite 3.8.9 which was just released on 4/8/2015 as gold has changed behavior with index_list() functionality by adding 2 more columns of data the returned queryset.  This breaks introspection.py with too many values to unpack.  A PR has been prepared that fixes this for both the new version and older behavior of Sqlite.

The question is should this be backported.  If this bug had been found before the release of Django 1.8, it would have been a blocker for the release. It's clearly a blocking bug and the test suite fail whaled in a few places if your python version was compiled with the newest version of Sqlite.  I think it should be backported to 1.8.  We could document it as an issue for 1.7, but if any security releases need to be made for 1.7 -- it might make sense to me backport it.  I know it's famous last words, but the fix is extremely small so I don't expect any regression since it handles both the old and new behavior from Sqlite.  If anyone can prove otherwise, I'll happily eat my own code fix ;-)

Sqlite usually does 12-15 releases a year.  We've had 5 so far in 2015.  So I suspect we'll see it in the wild with increasing frequency in the coming months as we have 7-10 more Sqlite releases to expect in 2015 if we don't backport it to at least 1.8.

@Tim, since you were the release manager for 1.8 -- what are your thoughts? I defer to those more in the know.

[Markus Holtermann]

For reference, Tim just backported your patch to 1.7 and 1.8.

/Markus