| Lucas_Werkmeister_WMDE closed this task as "Declined". Lucas_Werkmeister_WMDE added a comment. |
I think I’ll decline this issue:
- It’s no longer clear to me how effective it would even be. Certain constraints, like “symmetric” and “inverse”, cannot be satisfied in a single edit. We also use WDQS for several constraint checks, where we don’t have any way of specifying former revision IDs.
- It sounds like a performance nightmare. We would be sending 50 wbcheckconstraints requests simultaneously every time someone looked at a history page, recent changes, or a user’s contributions. In the case of a history page, all those requests would be for the same entity, which could be a very large one (an uncached constraint check on Q42 currently takes some twelve seconds). And all of these results would either have to be cached separately, or bypass the cache.
TASK DETAIL
EMAIL PREFERENCES
To: Lucas_Werkmeister_WMDE
Cc: CXuesong, Lydia_Pintscher, Jonas, Lucas_Werkmeister_WMDE, Aklapper, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Agabi10, Wikidata-bugs, aude, Mbch331
Cc: CXuesong, Lydia_Pintscher, Jonas, Lucas_Werkmeister_WMDE, Aklapper, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Agabi10, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
