jsTree-demo, poorly optimized or is it just me?
It felt like 99% of everything I do with jQuery involves a database some tree-structure so I figured I'd try jsTree out. I uploaded the demo and the way it seem to work is for every parent in the tree it calls a function get_children (PHP) with AJAX which makes a SELECT-query for that node to get the immediate children.
Am I missing something or isn't that extremely demanding on the database? The way I always do is get as much as I can from the database in one go then put it into PHP-arrays. With that plugin as I've seen a lot is that they put all the database-calls inside a class, do all those queries get pre-loaded or something when you call "new Database"? Or is a SELECT-query for a few rows just not that demanding at all?
I'm asking because I assume the ones that did jsTree are much better programmers than me and I hope to learn something :)
Am I missing something or isn't that extremely demanding on the database? The way I always do is get as much as I can from the database in one go then put it into PHP-arrays. With that plugin as I've seen a lot is that they put all the database-calls inside a class, do all those queries get pre-loaded or something when you call "new Database"? Or is a SELECT-query for a few rows just not that demanding at all?
I'm asking because I assume the ones that did jsTree are much better programmers than me and I hope to learn something :)
Topic Participants
daver690
Kevin Boudloche