django/docs/releases/2.1.5.txt

==========================
Django 2.1.5 release notes
==========================

*Expected January 1, 2019*


Django 2.1.5 fixes several bugs in 2.1.4.

Bugfixes
========

* Fixed compatibility with mysqlclient 1.3.14 (:ticket:`30013`).

* Fixed a schema corruption issue on SQLite 3.26+. You might have to drop and
  rebuild your SQLite database if you applied a migration while using an older
  version of Django with SQLite 3.26 or later (:ticket:`29182`).

* Prevented SQLite schema alterations while foreign key checks are enabled to
  avoid the possibility of schema corruption (:ticket:`30023`).

* Fixed a regression in Django 2.1.4 (which enabled keep-alive connections)
  where request body data isn't properly consumed for such connections
  (:ticket:`30015`).
Added stub release notes for 2.1.5 release. 2018-12-04 14:59:37 +00:00			`==========================`
			`Django 2.1.5 release notes`
			`==========================`

			`Expected January 1, 2019`


			`Django 2.1.5 fixes several bugs in 2.1.4.`

			`Bugfixes`
			`========`

Fixed #30013 -- Fixed DatabaseOperations.last_executed_query() with mysqlclient 1.3.14+. 2018-12-05 18:14:47 +00:00			* Fixed compatibility with mysqlclient 1.3.14 (:ticket:`30013`).
Fixed #29182 -- Fixed schema table alteration on SQLite 3.26+. SQLite 3.26 repoints foreign key constraints on table renames even when foreign_keys pragma is off which breaks every operation that requires a table rebuild to simulate unsupported ALTER TABLE statements. The newly introduced legacy_alter_table pragma disables this behavior and restores the previous schema editor assumptions. Thanks Florian Apolloner, Christoph Trassl, Chris Lamb for the report and troubleshooting assistance. 2018-12-06 16:37:43 +00:00
			`* Fixed a schema corruption issue on SQLite 3.26+. You might have to drop and`
			`rebuild your SQLite database if you applied a migration while using an older`
			version of Django with SQLite 3.26 or later (:ticket:`29182`).
Fixed #30023 -- Prevented SQLite schema alterations while foreign key checks are enabled. Prior to this change foreign key constraint references could be left pointing at tables dropped during operations simulating unsupported table alterations because of an unexpected failure to disable foreign key constraint checks. SQLite3 does not allow disabling such checks while in a transaction so they must be disabled beforehand. Thanks ezaquarii for the report and Carlton and Tim for the review. 2018-12-08 00:55:47 +00:00
			`* Prevented SQLite schema alterations while foreign key checks are enabled to`
			avoid the possibility of schema corruption (:ticket:`30023`).
Refs #30015 -- Added 2.1.5 release note and removed 'we' in comments. 2018-12-20 09:02:45 +00:00
			`* Fixed a regression in Django 2.1.4 (which enabled keep-alive connections)`
			`where request body data isn't properly consumed for such connections`
			(:ticket:`30015`).