On 12/13/10 4:07 PM, Brion Vibber wrote:
I think I've worked out how to make human-friendly time-based sorting
work efficiently in the database while remaining compatible with how
client apps using the Twitter-compatible API expect to use the
'since_id' and 'max_id' parameters.
In most cases this should work 'naturally' for new messages, while
allowing older messages to still be accessed:
http://status.net/wiki/Sorting_changes
I've now committed these changes on 0.9.x branch in git.
db/096to097.sql tweaks indexes on several tables, but smaller sites
should still be able to run on the updated code without applying the
changes.
Large sites will definitely want the index updates, as without them
there may be performance regressions on public, user-profile, group, and
tag timelines.
(Tag filtering within a group or user's stream is still going to be not
quite as efficient as one might like, needing some more stuff.)
I've also added indexes cleaning up a couple of queries that weren't
well indexed in the past, including fetching conversations and pulling
your groups list for the sidebar.
-- brion
_______________________________________________
StatusNet-dev mailing list
StatusNet-dev@lists.status.net
http://lists.status.net/mailman/listinfo/statusnet-dev
