django_evolution.support
Constants indicating available Django features.
Module Attributes
Index names changed in Django 1.5, with the introduction of index_together. |
|
Whether new-style Index classes are available. |
|
Whether Q() objects can be directly compared. |
|
Whether F() objects can be directly compared. |
|
Whether new-style Constraint classes are available. |
|
Whether database table comments are available. |
|
Whether built-in support for Django Migrations is present. |
Functions
|
Return whether Index supports a specific attribute. |
- django_evolution.support.supports_index_together = True
Index names changed in Django 1.5, with the introduction of index_together.
- django_evolution.support.supports_indexes = True
Whether new-style Index classes are available.
Django 1.11 introduced formal support for defining explicit indexes not bound to a field definition or as part of
index_together/unique_together.- Type:
- django_evolution.support.supports_q_comparison = True
Whether Q() objects can be directly compared.
Django 2.0 introduced this support.
- Type:
- django_evolution.support.supports_f_comparison = True
Whether F() objects can be directly compared.
Django 2.0 introduced this support.
- Type:
- django_evolution.support.supports_constraints = True
Whether new-style Constraint classes are available.
Django 2.2 introduced formal support for defining explicit constraints not bound to a field definition.
- django_evolution.support.supports_db_table_comments = False
Whether database table comments are available.
Django 4.2 introduced formal support for setting comments attached to tables.
Support may vary by database backend.
New in version 2.3.
- Type:
- django_evolution.support.supports_migrations = True
Whether built-in support for Django Migrations is present.
This is available in Django 1.7+.