Hope this forward makes it to the mailing list.This is something I thought I'd share as part of a discussion with Kieren. If anyone has better approaches for what we're accomplishing (in the speed we're accomplishing it) I'm humble enough to listen. ;-)
I'll note one thing I am aware of is that FOUND_ROWS() is available to us in the newer versions of MySQL. I tested the real speed and it wasn't much different in practice so I haven't given it any priority at all yet.
Something that might not be obvious to people not working on the project is how intensive the privacy feature is on the SQL. This is for a logged in user - a visitor gets a slightly simpler query with respect to privacy because we have a cheat column for them, but it still has to check private_until because that changes with time. A cron job could update a more sophisticated cheat column but we haven't done that yet.
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ Connotea-code-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/connotea-code-devel
