Comment 7 for bug 1695911

I may be oversimplifying the issue, but my understanding of the browse_entry_sort_value_value_key index is that it acts purely as a unique constraint. The MD5 variant seems to handle that OK.

In my current code, I have not modified browse_entry_sort_value_idx, the one I assume is used by the search queries. It still contains the full value.

I'd be happy to run a query, Mike, if there's something you'd like me to test. This code is on a dev VM at the moment, but should be up on a large DB soon.