Am 19.09.2017 um 10:15 schrieb Jaime Crespo:
I am not a mediawiki developer, but shouldn't sha1
be moved instead of
deleted/not deleted? Moved to the content table- so it is kept
The background of my original mail is indede the question whether we
sha1 field in the content table. The current draft of the DB schema includes it.
That table will be tall, and the sha1 is the (on average) largest field. If we
are going to use a different mechanism for tracking reverts soon, my hope was
that we can do without it.
OIn any case, my impression is that if we want to keep using hashes to detect
reverts, we need to keep rev_sha1 - and to maintain is, we ALSO need content_sha1.
Principal Platform Engineer
Gesellschaft zur Förderung Freien Wissens e.V.