| Smalyshev added a comment. |
When a constraint check is executed for an Item the result will be stored and the old result for that Item will be deleted.
So, constraint checks are bound to existing items? I wonder if it would be possible to expose them in the same way page properties are exposed.
It will never be imported and it will never be complete.
It is just a snapshot.
But a snapshot of what? Right now we can (and do) delete the whole database, reimage any host and restore it from latest dump + RC feed + category dump. However, neither of those contains constraint checks data. So how this would be managed?
Access will only be allowed from within the cluster.
Still, this means we need to create non-local write interface that previously didn't exist, and put access controls (by IP or otherwise) to it. Will need to research how easy that would be...
Cc: Lucas_Werkmeister_WMDE, Gehel, Smalyshev, Jonas, Aklapper, Lahi, Gq86, Darkminds3113, GoranSMilovanovic, QZanden, EBjune, merbst, LawExplorer, Avner, Agabi10, FloNight, Xmlizer, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles, Mbch331
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
