| Lucas_Werkmeister_WMDE added a comment. |
We primarily need a key-value store, yes: given an entity ID, get the constraints data for that entity.
However, that data also includes some metadata on the validity of the constraints data, specifically a set of other entity IDs with their latest revision IDs at the time of the constraint check: if any of those entities have been edited since then (i. e., the latest revision ID is no longer the one stored in the metadata), the cached/stored results are stale and should not be used. This covers the case of constraint definitions changing (constraint definitions are statements on properties, so any change to the constraint definitions means a new revision on a property page), but also other changes (e. g. if there is a constraint “the value entity of this statement must have a statement X”, then the results are stale if the entity in the statement value was edited).
Currently, these metadata checks are done when constraint check results for an entity are requested, but ideally there would also be a way to mass-refresh all related constraint check results when an entity is updated. This might require storing that metadata in a different place.
Cc: Smalyshev, Eevans, daniel, mobrovac, Jonas, Lucas_Werkmeister_WMDE, Aklapper, Addshore, Lahi, Gq86, GoranSMilovanovic, QZanden, merbst, LawExplorer, Agabi10, Hardikj, Wikidata-bugs, aude, Lydia_Pintscher, Mbch331, fgiunchedi
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
