p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Removed outdated note about not supporting partial indexes by Django. 

Supported since a906c98982.
This commit is contained in:
Mariusz Felisiak 2020-02-29 20:35:11 +01:00 committed by GitHub
parent e65fea9292
commit a49c2b6bf0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/ref/migration-operations.txt
View File

@ -246,8 +246,7 @@ Special Operations
.. class:: RunSQL(sql, reverse_sql=None, state_operations=None, hints=None, elidable=False) .. 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 Allows running of arbitrary SQL on the database - useful for more advanced
features of database backends that Django doesn't support directly, like features of database backends that Django doesn't support directly.
partial indexes.
``sql``, and ``reverse_sql`` if provided, should be strings of SQL to run on ``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 the database. On most database backends (all but PostgreSQL), Django will