Last modified: 2013-06-06 06:07:57 UTC
I would want revision.rev_sha1 exposed in the api, so I can retrieve revisions which contains the same content (I assume rev_sha1 is the sha1 of the content and thus should be same for different revisions with the same content)
I meant expose it as field for query so you can limit the query to sha1
This would probably require adding an index covering it, as it's currently not indexed at all (although img_sha1 is).
(In reply to comment #1) > I meant expose it as field for query so you can limit the query to sha1 Good thing you clarified, I was about to close this as a dup of bug 21860. What exactly is the use case for this, that isn't served by processing the output of prop=revisions&rvprop=sha1 on the client? (In reply to comment #2) > This would probably require adding an index covering it, as it's currently > not indexed at all (although img_sha1 is). That is correct.
Sometimes there can be way too many revisions to practically loop through them all to find out which one is the oldest one. For example in a edit war/revert war, I would want to be able to quickly get the original revision which started it all, and of someone reverts to a really old revision, it's good to be able to quickly find out whom made that revision in case of sockery
If rev_sha1 will always be queried with a page id, a (rev_page, rev_sha1(5)) index should be fine, even on enwiki.
