Range checks (“range” or “difference within range” constraint type) can involve the current time as a range endpoint (e. g. “date of spacecraft launch must be between 4 October 1957 and the current day”). Currently, we cache those results just like any other result, even though the validity of the result can change as the current date changes (a violation can turn into a compliance). We need to do some special handling for this.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Lucas_Werkmeister_WMDE | T173695 Enable constraint checks by default for users | |||
| Open | None | T103228 Improve performance of constraint check | |||
| Resolved | Lydia_Pintscher | T179839 Cache constraint check results | |||
| Resolved | Lydia_Pintscher | T179849 Cache all constraint check results per-entity | |||
| Resolved | Lucas_Werkmeister_WMDE | T181060 Cache constraint check results per-entity in ObjectCache (L) (days: 2) | |||
| Resolved | Lucas_Werkmeister_WMDE | T184812 Enable constraint result caching on Wikidata | |||
| Resolved | Lucas_Werkmeister_WMDE | T187057 Constraint check results involving the current time are cached indiscriminately [M] | |||
| Resolved | Lucas_Werkmeister_WMDE | T187058 Introduce separate messages for range violations involving current time | |||
| Resolved | Lucas_Werkmeister_WMDE | T186008 Remove range in numerical notation from violation messages | |||
| Resolved | Lucas_Werkmeister_WMDE | T187061 Don’t cache constraint check results involving current time whose validity will change soon |