You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could get more specific about which element queries need to be executed during a cache refresh, thus reducing the processing time. For example, entry queries are ordered by post date by default, meaning that if an entry is updated but its post date has not changed, then entry queries with an orderBy set to postDate can be ignored.
This applies to entry queries such as the following.
As of version 4.4.0, Blitz automatically tracks which attributes and custom fields are used in each element query, as well as which attributes and custom fields are changed on each element save, greatly reducing the number of element queries that must be executed during the cache refresh process.
We could get more specific about which element queries need to be executed during a cache refresh, thus reducing the processing time. For example, entry queries are ordered by post date by default, meaning that if an entry is updated but its post date has not changed, then entry queries with an
orderBy
set topostDate
can be ignored.This applies to entry queries such as the following.
But not to the following, since they rely on attributes and custom fields.
We could, however, make the same checks on attributes such as
title
,slug
,dateCreated
, etc.The text was updated successfully, but these errors were encountered: