Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

[1.9.x] Refs #26034 -- Added another case fixed by this ticket to release notes.

Browse Source 
Thanks Shai Berger for the report.

Backport of 497b5d6feee5b7947231bd0ae6edf833773b6cce and
5e8685c1b14e94e3f540ac1d68b61e71dcc27517 from master
This commit is contained in:
Tim Graham 2016-01-25 08:33:02 -05:00
parent 41e059de7c
commit 4aec49d015
2 changed files with 12 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/releases/1.8.9.txt
View File

@ -19,10 +19,12 @@ Bugfixes
the admin calendar widget for timezones from GMT+0100 to GMT+1200
(:ticket:`24980`).
* Fixed incorrect index handling in migrations on PostgreSQL when adding
``db_index=True`` or ``unique=True`` to a ``CharField`` or ``TextField`` that
already had the other specified, or when removing one of them from a field
that had both (:ticket:`26034`).
* Fixed a regression in 1.8.8 causing incorrect index handling in migrations on
PostgreSQL when adding ``db_index=True`` or ``unique=True`` to a
``CharField`` or ``TextField`` that already had the other specified, or when
removing one of them from a field that had both, or when adding
``unique=True`` to a field already listed in ``unique_together``
(:ticket:`26034`).
* Fixed a crash when using an ``__in`` lookup inside a ``Case`` expression
(:ticket:`26071`).

10
docs/releases/1.9.2.txt
View File

@ -26,10 +26,12 @@ Bugfixes
escaped value to be displayed in the select dropdown of the parent window
(:ticket:`25997`).
* Fixed incorrect index handling in migrations on PostgreSQL when adding
``db_index=True`` or ``unique=True`` to a ``CharField`` or ``TextField`` that
already had the other specified, or when removing one of them from a field
that had both (:ticket:`26034`).
* Fixed a regression in 1.8.8 causing incorrect index handling in migrations on
PostgreSQL when adding ``db_index=True`` or ``unique=True`` to a
``CharField`` or ``TextField`` that already had the other specified, or when
removing one of them from a field that had both, or when adding
``unique=True`` to a field already listed in ``unique_together``
(:ticket:`26034`).
* Fixed a regression where defining a relation on an abstract model's field
using a string model name without an app_label no longer resolved that