These fields are None by default and the invalidation criteria (here and here) is “being equal to None”, so there will always be extra SQL queries for schedules that are either empty or have no overrides. If this is fixed, these extra SQL queries to custom oncall shifts would disappear, making loading schedules more efficient.
These fields are
None
by default and the invalidation criteria (here and here) is “being equal to None”, so there will always be extra SQL queries for schedules that are either empty or have no overrides. If this is fixed, these extra SQL queries to custom oncall shifts would disappear, making loading schedules more efficient.