    ``DatabaseClient.settings_to_cmd_args_env()`` method. Third-party database
    backends must implement ``DatabaseClient.settings_to_cmd_args_env()`` or
    override ``DatabaseClient.runshell()``.
  
  :mod:`django.contrib.admin`
  ---------------------------
  
  * Pagination links in the admin are now 1-indexed instead of 0-indexed, i.e.
    the query string for the first page is ``?p=1`` instead of ``?p=0``.
  
 
</s> remove     supports_expression_indexes = False
 </s> add     supports_expression_indexes = True </s> remove     supports_expression_indexes = True
 </s> add  </s> remove     supports_expression_indexes = True
 </s> add  </s> remove     supports_expression_indexes = True
 </s> add 
* Third-party database backends must implement support for functional indexes
  (:attr:`.Index.expressions`) or set
  ``DatabaseFeatures.supports_expression_indexes`` to ``False``. If ``COLLATE``
  is not a part of the ``CREATE INDEX`` statement, set
  ``DatabaseFeatures.collate_as_index_expression`` to ``True``.

    ``DatabaseClient.settings_to_cmd_args_env()`` method. Third-party database
    backends must implement ``DatabaseClient.settings_to_cmd_args_env()`` or
    override ``DatabaseClient.runshell()``.
  
* Third-party database backends must implement support for functional indexes
  (:attr:`.Index.expressions`) or set
  ``DatabaseFeatures.supports_expression_indexes`` to ``False``. If ``COLLATE``
  is not a part of the ``CREATE INDEX`` statement, set
  ``DatabaseFeatures.collate_as_index_expression`` to ``True``.

  :mod:`django.contrib.admin`
  ---------------------------
  
  * Pagination links in the admin are now 1-indexed instead of 0-indexed, i.e.
    the query string for the first page is ``?p=1`` instead of ``?p=0``.
  
keep keep keep add keep keep keep keep keep keep
 Refs #26167 -- Changed default value of DatabaseFeatures.supports_expression_indexes to True. 
docs/releases/3.2.txt