Fixed #28714 -- Added system checks for invalid model field names in Meta.indexes.

Thanks Gabriel for the report and Adam Johnson for the review.
This commit is contained in:
hui shang 2017-12-28 07:56:24 +08:00 committed by Tim Graham
parent 1d00923848
commit f1aa58479c
3 changed files with 63 additions and 3 deletions

View file

@ -265,16 +265,16 @@ Models
* **models.E009**: All ``index_together`` elements must be lists or tuples.
* **models.E010**: ``unique_together`` must be a list or tuple.
* **models.E011**: All ``unique_together`` elements must be lists or tuples.
* **models.E012**: ``index_together/unique_together`` refers to the
* **models.E012**: ``indexes/index_together/unique_together`` refers to the
nonexistent field ``<field name>``.
* **models.E013**: ``index_together/unique_together`` refers to a
* **models.E013**: ``indexes/index_together/unique_together`` refers to a
``ManyToManyField`` ``<field name>``, but ``ManyToManyField``\s are not
supported for that option.
* **models.E014**: ``ordering`` must be a tuple or list (even if you want to
order by only one field).
* **models.E015**: ``ordering`` refers to the nonexistent field
``<field name>``.
* **models.E016**: ``index_together/unique_together`` refers to field
* **models.E016**: ``indexes/index_together/unique_together`` refers to field
``<field_name>`` which is not local to model ``<model>``.
* **models.E017**: Proxy model ``<model>`` contains model fields.
* **models.E018**: Autogenerated column name too long for field ``<field>``.