From bbfcd9618b06556a0ae2c38456ef38bf3bea9e9d Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Sat, 11 Apr 2015 16:10:31 +0200 Subject: [1.8.x] Fixed #24595 -- Prevented loss of null info in MySQL field alteration Thanks Simon Percivall for the report, and Simon Charette and Tim Graham for the reviews. Backport of 02260ea3f6 from master. --- docs/releases/1.7.8.txt | 3 +++ docs/releases/1.8.1.txt | 3 +++ 2 files changed, 6 insertions(+) (limited to 'docs') diff --git a/docs/releases/1.7.8.txt b/docs/releases/1.7.8.txt index 912171f8da..dc281b6b62 100644 --- a/docs/releases/1.7.8.txt +++ b/docs/releases/1.7.8.txt @@ -10,3 +10,6 @@ Django 1.7.8 fixes: (:ticket:`24637`). * A database table name quoting regression in 1.7.2 (:ticket:`24605`). + +* Prevented the loss of ``null``/``not null`` column properties during field + alteration of MySQL databases (:ticket:`24595`). diff --git a/docs/releases/1.8.1.txt b/docs/releases/1.8.1.txt index 15b7546933..14d48a5ed7 100644 --- a/docs/releases/1.8.1.txt +++ b/docs/releases/1.8.1.txt @@ -55,3 +55,6 @@ Bugfixes ``qs.annotate(foo=F('field')).values('pk').order_by('foo'))`` (:ticket:`24615`). * Fixed a database table name quoting regression (:ticket:`24605`). + +* Prevented the loss of ``null``/``not null`` column properties during field + alteration of MySQL databases (:ticket:`24595`). -- cgit v1.3