Domas Mituzas wrote: >> * When reverting, do a select count(*) where md5=? and then do something >> more advanced when more than one match is found > > finally "we don't need an index on it" becomes "we need an index on it", and > storage efficiency becomes much more interesting (binary packing yay ;-) > > so, what are the use cases and how does one index for them? is it global hash > check, per page? etc > > Domas
I don't know why people have started asking about talking hashes when reverting. MediaWiki already knows in a rollback that the revision is identical to the previous one. It even avoids storing the same text twice. However, if you want to "check if something is a revert" say clearly that you are testing on every edit if there's a previous revision [for the same page?] with the same text. Is there a "something more advanced to be done" or just dreams? Would for instance the WikiTrust extension make use of it, or instead would need to store its own checksums on another table? PS: I don't consider bug 2939 a good need. I think it is good to see that there were messages. The provided usecase could be solved with rollback in bot mode. _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
