[Wikidata-bugs] [Maniphest] [Updated] T179849: Cache all constraint check results per-entity

2017-11-23 Thread Ladsgroup
Ladsgroup removed a project: Wikidata-Former-Sprint-Board. TASK DETAILhttps://phabricator.wikimedia.org/T179849EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: LadsgroupCc: hoo, Ladsgroup, Jonas, Aklapper, Lucas_Werkmeister_WMDE, Lahi, Gq86, GoranSMilovanovic,

[Wikidata-bugs] [Maniphest] [Updated] T179849: Cache all constraint check results per-entity

2017-11-21 Thread Lucas_Werkmeister_WMDE
Lucas_Werkmeister_WMDE added a comment. Note: we’ve decided to go ahead with the ObjectCache for now, and store what would be wbqc_result above in the cache instead: see T181060: Cache constraint check results per-entity in ObjectCache (L). We can migrate that to the database, as described above,

[Wikidata-bugs] [Maniphest] [Updated] T179849: Cache all constraint check results per-entity

2017-11-16 Thread Lucas_Werkmeister_WMDE
Lucas_Werkmeister_WMDE added a comment. Here are the result statuses of 100 randomly chosen items (P6333): "bad-parameters" 15 "warning" 66 "not-main-snak" 1601 "todo" 26 "compliance" 5096 It appears the average item has plenty of checkable snaks, but very few violations (which is great!). So

[Wikidata-bugs] [Maniphest] [Updated] T179849: Cache all constraint check results per-entity

2017-11-15 Thread Lucas_Werkmeister_WMDE
Lucas_Werkmeister_WMDE added a comment. Do we really want to cache all constraint check results… or only those that we will actually show in the gadget: warning, violation and bad-parameters? For reference: Berlin (Q64) currently has the following distribution of result statuses (P6320): 1344

[Wikidata-bugs] [Maniphest] [Updated] T179849: Cache all constraint check results per-entity

2017-11-08 Thread Lucas_Werkmeister_WMDE
Lucas_Werkmeister_WMDE added a comment. Oh, and another thing – I suppose we also need to invalidate the cached results somehow when a constraint statement is edited. I’m not sure what the most efficient way to do that is. Explicitly purge cached results when a constraint statement is edited.

[Wikidata-bugs] [Maniphest] [Updated] T179849: Cache all constraint check results per-entity

2017-11-07 Thread Franziska_Heine
Franziska_Heine added a project: Wikidata-Test-Sprint. TASK DETAILhttps://phabricator.wikimedia.org/T179849EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Franziska_HeineCc: Jonas, Aklapper, Lucas_Werkmeister_WMDE, Lahi, GoranSMilovanovic, QZanden, Agabi10,

[Wikidata-bugs] [Maniphest] [Updated] T179849: Cache all constraint check results per-entity

2017-11-07 Thread Lucas_Werkmeister_WMDE
Lucas_Werkmeister_WMDE added a project: Wikidata-Sprint. TASK DETAILhttps://phabricator.wikimedia.org/T179849EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Lucas_Werkmeister_WMDECc: Jonas, Aklapper, Lucas_Werkmeister_WMDE, Lahi, GoranSMilovanovic, QZanden,