his DOM implementation is just like your average DOM except that it can store the parsed node data to a file somewhere. Most DOM implementations store their parsed node data in RAM, meaning the the available RAM in the computer limits the size of the XML file that it can create or parse.
文 件 列 表
docs api ClassDiagrams.vsd manual.html build.xml diskdom.jar src au
SHOW FULL COLUMNS FROM `jrk_downrecords` [ RunTime:0.001232s ]
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.131463s ]
SHOW FULL COLUMNS FROM `jrk_tagrecords` [ RunTime:0.001743s ]
SELECT * FROM `jrk_tagrecords` WHERE `status` = 1 ORDER BY `num` DESC LIMIT 20 [ RunTime:0.003272s ]
SHOW FULL COLUMNS FROM `jrk_member` [ RunTime:0.001780s ]
SELECT `id`,`username`,`userhead`,`usertime` FROM `jrk_member` WHERE `status` = 1 ORDER BY `usertime` DESC LIMIT 10 [ RunTime:0.006244s ]
SHOW FULL COLUMNS FROM `jrk_searchrecords` [ RunTime:0.001506s ]
SELECT * FROM `jrk_searchrecords` WHERE `status` = 1 ORDER BY `num` DESC LIMIT 5 [ RunTime:0.005879s ]
SELECT aid,title,count(aid) as c FROM `jrk_downrecords` GROUP BY `aid` ORDER BY `c` DESC LIMIT 10 [ RunTime:0.025062s ]
SHOW FULL COLUMNS FROM `jrk_articles` [ RunTime:0.002037s ]
UPDATE `jrk_articles` SET `hits` = 1 WHERE `id` = 78628 [ RunTime:0.001650s ]
