No index needed ? If we want to re-use text-table rows and query by a generated hash when saving the revision text, we would need an index, right ?
Topic on Talk:Requests for comment/Database field for checksum of page text
Yes, if you want to query by hash then you would need obviously an index but I haven't heard a use case yet where we really would want to query often the hash column. In addition, the checksum will not be always unique across different pages. If two different pages have been blanketed then they would have the same hash. So we might need a compounded index in that case but I would like to hear more different use cases first before we decide on including an index.
@Dantman, thanks for reminding me, I've added the bugreport link to the proposal.
I'm not aware of any analyzes that needs to query for a specific hash value, all I've seen needs a list of hashes through the history of an article. I can imagine one situation where it is interesting and that is identifying an undo or save of an old version as an identity revert. Such reverts are not that uncommon, and I think they should be identified and tagged if possible.