My applications will have an impact in the SQL queries. Right now, to display tweets in reverse chronological order and with pagination, my query has something like this:
SELECT * FROM tweets INNER JOIN mytable on tweets.id = mytable.tweet_id GROUP BY tweets.id ORDER BY tweets.id DESC LIMIT 100, 20 Having the group and order clause on the same field (tweets.id) improves the performance. But after this change, I'm forced to use the timestamp in the ORDER clause. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.