entites are modeled runtime, and a front end will fetch the data from teh server and provide the basic modes of primitive operations (creation retrieval updation and deletion). this is still under development.
if you are reading this, thanks for hte consideration. i am still working on this and is not developed completely
SHOW FULL COLUMNS FROM `jrk_downrecords` [ RunTime:0.001092s ]
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.077929s ]
SHOW FULL COLUMNS FROM `jrk_tagrecords` [ RunTime:0.001118s ]
SELECT * FROM `jrk_tagrecords` WHERE `status` = 1 ORDER BY `num` DESC LIMIT 20 [ RunTime:0.001267s ]
SHOW FULL COLUMNS FROM `jrk_member` [ RunTime:0.001067s ]
SELECT `id`,`username`,`userhead`,`usertime` FROM `jrk_member` WHERE `status` = 1 ORDER BY `usertime` DESC LIMIT 10 [ RunTime:0.003131s ]
SHOW FULL COLUMNS FROM `jrk_searchrecords` [ RunTime:0.000889s ]
SELECT * FROM `jrk_searchrecords` WHERE `status` = 1 ORDER BY `num` DESC LIMIT 5 [ RunTime:0.003784s ]
SELECT aid,title,count(aid) as c FROM `jrk_downrecords` GROUP BY `aid` ORDER BY `c` DESC LIMIT 10 [ RunTime:0.014716s ]
SHOW FULL COLUMNS FROM `jrk_articles` [ RunTime:0.001274s ]
UPDATE `jrk_articles` SET `hits` = 2 WHERE `id` = 255976 [ RunTime:0.017083s ]