El 5/12/09 3:01 PM, Aryeh Gregor escribió:
On Tue, May 12, 2009 at 5:46 PM, Brion Vibberbrion@wikimedia.org wrote:
As a general issue we also need to consider managing paging through collation-sorted lists, since sort keys for different inputs may produce the same result. At the moment I think category lists are paged by offset (bad!) but we should ensure this is planned for.
Category lists use Pager, so they're paged by index offsets, not LIMIT M, N. Note that they should probably be ordered by (cl_sortkey, cl_from) or something instead of just (cl_sortkey) -- currently, equal sortkeys will cause problems. But Pager doesn't support multi-key sort right now.
Ah, even better -- it's already broken! :)
You don't need another column for categorylinks, you can use the existing cl_sortkey, so that should be relatively easy to deploy. It doesn't help with non-category use cases, of course.
You would if you need to store a processed sort key index that's not in the form of displayable characters. (eg, the output of the UCA)
Why? cl_sortkey isn't ever displayed to the user
It sure is -- the first letter of each sort key entry is displayed in a nice large type in the category list.
-- brion