What option disables the following query:
SELECT COUNT(DISTINCT(userid)) AS count FROM vb_session WHERE vb_session.userid>0 AND vb_session.lastactivity>1245253343;
Does this have to do with dispalying the active members on the site?
I am currently having some memory issues that are being worked on but i don't want vbulletin to call the function that does this query until i get my optimization issues resolved...
SELECT COUNT(DISTINCT(userid)) AS count FROM vb_session WHERE vb_session.userid>0 AND vb_session.lastactivity>1245253343;
Does this have to do with dispalying the active members on the site?
I am currently having some memory issues that are being worked on but i don't want vbulletin to call the function that does this query until i get my optimization issues resolved...
Comment