I’ve had another look at this, and it seems (in its simplest form) to be topic.word_count multiplied by the ‘read time word count’ admin setting (default 500 word/min). So I think this query would produce the top X ‘longest to read’ topics:
-- [params]
-- integer :limit = 10
SELECT t.id as topic_id, (t.word_count)/500+1 AS estimated_read_time
FROM topics t
WHERE t.word_count IS NOT NULL
AND t.archetype = 'regular'
ORDER BY t.word_count DESC
LIMIT :limit
Though there’s also the alternative ‘4 second minimum’ too: (amount of posts x 4)/60. Which is there to account for photo topics with no word count. So it works out both, and displays whichever is larger. But I haven’t quite worked out how to add that in yet. ![]()
Unfortunately, I haven’t got a large enough site to test it out on properly. It seemed to work on a small test sample, but it may need tweaking. ![]()
Edit: I added in a ‘limit’ parameter to make it closer to the OP spec. ![]()