It is not the intention of this application note to illustrate usage
of the part in either of operational modes. The application
note does not cover details on setting up for data transfers.
After having reviewed this application note, the reader is
expected to understand the data flow for and IN and OUT
SHOW FULL COLUMNS FROM `jrk_downrecords` [ RunTime:0.001919s ]
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.096027s ]
SHOW FULL COLUMNS FROM `jrk_tagrecords` [ RunTime:0.001047s ]
SELECT * FROM `jrk_tagrecords` WHERE `status` = 1 ORDER BY `num` DESC LIMIT 20 [ RunTime:0.001309s ]
SHOW FULL COLUMNS FROM `jrk_member` [ RunTime:0.001267s ]
SELECT `id`,`username`,`userhead`,`usertime` FROM `jrk_member` WHERE `status` = 1 ORDER BY `usertime` DESC LIMIT 10 [ RunTime:0.003241s ]
SHOW FULL COLUMNS FROM `jrk_searchrecords` [ RunTime:0.000968s ]
SELECT * FROM `jrk_searchrecords` WHERE `status` = 1 ORDER BY `num` DESC LIMIT 5 [ RunTime:0.003838s ]
SELECT aid,title,count(aid) as c FROM `jrk_downrecords` GROUP BY `aid` ORDER BY `c` DESC LIMIT 10 [ RunTime:0.014353s ]
SHOW FULL COLUMNS FROM `jrk_articles` [ RunTime:0.001053s ]
UPDATE `jrk_articles` SET `hits` = 2 WHERE `id` = 532218 [ RunTime:0.013259s ]
