From a49c2b6bf098eb48c07641f60dba9be78c6cc92f Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Sat, 29 Feb 2020 20:35:11 +0100 Subject: [PATCH] Removed outdated note about not supporting partial indexes by Django. Supported since a906c9898284a9aecb5f48bdc534e9c1273864a6. --- docs/ref/migration-operations.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/ref/migration-operations.txt b/docs/ref/migration-operations.txt index f082452a31f..148ac958395 100644 --- a/docs/ref/migration-operations.txt +++ b/docs/ref/migration-operations.txt @@ -246,8 +246,7 @@ Special Operations .. class:: RunSQL(sql, reverse_sql=None, state_operations=None, hints=None, elidable=False) Allows running of arbitrary SQL on the database - useful for more advanced -features of database backends that Django doesn't support directly, like -partial indexes. +features of database backends that Django doesn't support directly. ``sql``, and ``reverse_sql`` if provided, should be strings of SQL to run on the database. On most database backends (all but PostgreSQL), Django will