Releases: W1ldPo1nter/django-queryable-properties
Releases · W1ldPo1nter/django-queryable-properties
django-queryable-properties 1.8.0
- Added support for Django 4.0
- Added new ready-to-use queryable property implementations for properties based on subqueries
(SubqueryFieldProperty
,SubqueryExistenceCheckProperty
) RelatedExistenceCheckProperty
objects can now be configured as negated to be able to check for the non-existence
of related objects
django-queryable-properties 1.7.1
- Added support for Python 3.10
- Fixed duplicate selections of
GROUP BY
columns when multiple aggregate properties are selected, which also led to
wrong property values, in Django versions below 1.8
django-queryable-properties 1.7.0
- Added the
prefetch_queryable_properties
utility function which allows to efficiently query property values for
model instances that were already loaded from the database beforehand - Extended the
LookupFilterMixin
to allow to define a filter function/method that handles all lookups that don't
use an explicitly registered function/method - Values for queryable properties with setters can now also be set using initializer keyword arguments of their
respective models
django-queryable-properties 1.6.1
- Fixed the
AnnotationGetterMixin
and its subclasses to be able to work with nested properties correctly regardless
of whether or not the model's base manager uses the queryable properties extensions - Fixed the admin filter that displays all possible options to be able to work with nested properties correctly
regardless of whether or not the model's default manager uses the queryable properties extensions
django-queryable-properties 1.6.0
- Added support for Django 3.2
- Queryable properties can now define a verbose name that can be used in UI representations
- Added a Django admin integration that allows to reference queryable properties like regular model fields in various
admin options - Fixed the construction of
GROUP BY
clauses when using annotations based on aggregate queryable properties in
Django 1.8