On 5 Feb 2003, Brion Vibber wrote:
However a very active user who becomes inactive, and
falls out of
recentchanges, would still be slow to query. Jan and Lars have suggested
using compound indexes which include the timestamp fields _and_ the user
fields so it can both select and sort using the index, and that sounds
reasonable in a sick sort of database-logic way. :)
Might it be possible to store all changes _already sorted_ by date? Then one
could just show the first 50 (or last 50 depending on sort order) hits
without the need of any further selection or sorting.
Andre Engels