Alerteon is closed down and will no longer be developed. This project never worked out the way that I had hoped. I think the best way to handle logging is to take the processing of logging outside the application and into something more robust like Logstash.
SHOW FULL COLUMNS FROM `jrk_downrecords` [ RunTime:0.001231s ]
SELECT `a`.`aid`,`a`.`title`,`a`.`create_time`,`m`.`username` FROM `jrk_downrecords` `a` INNER JOIN `jrk_member` `m` ON `a`.`uid`=`m`.`id` WHERE `a`.`status` = 1 GROUP BY `a`.`aid` ORDER BY `a`.`create_time` DESC LIMIT 10 [ RunTime:0.090346s ]
SHOW FULL COLUMNS FROM `jrk_tagrecords` [ RunTime:0.001182s ]
SELECT * FROM `jrk_tagrecords` WHERE `status` = 1 ORDER BY `num` DESC LIMIT 20 [ RunTime:0.001957s ]
SHOW FULL COLUMNS FROM `jrk_member` [ RunTime:0.001205s ]
SELECT `id`,`username`,`userhead`,`usertime` FROM `jrk_member` WHERE `status` = 1 ORDER BY `usertime` DESC LIMIT 10 [ RunTime:0.003964s ]
SHOW FULL COLUMNS FROM `jrk_searchrecords` [ RunTime:0.001050s ]
SELECT * FROM `jrk_searchrecords` WHERE `status` = 1 ORDER BY `num` DESC LIMIT 5 [ RunTime:0.003250s ]
SELECT aid,title,count(aid) as c FROM `jrk_downrecords` GROUP BY `aid` ORDER BY `c` DESC LIMIT 10 [ RunTime:0.014827s ]
SHOW FULL COLUMNS FROM `jrk_articles` [ RunTime:0.001341s ]
UPDATE `jrk_articles` SET `hits` = 1 WHERE `id` = 298858 [ RunTime:0.001268s ]
