If you're heavily skewed towards reads and not writes (as it seems in the case of a CMS), you might want to look at Celko nested sets:
http://www.intelligententerprise.com/001020/celko.jhtml http://dev.mysql.com/tech-resources/articles/hierarchical-data.html A little more work on updates than an adjacency model, but a lot more efficient. Derek On Sun, Nov 30, 2008 at 6:29 AM, Viktor Klang <[EMAIL PROTECTED]>wrote: > Hi Tim! > > I'm not sure I follow. What do you need the tree-structure for? > > /Vik > > On Sun, Nov 30, 2008 at 1:11 PM, Tim Perrett <[EMAIL PROTECTED]> wrote: > >> >> Hey Viktor, >> >> > If you use Hibernate you could simply configure the L2-cache and have >> > Hibernate manage it for you. (EHCache or whatever cache-provider you >> like) >> > This means you won't have to manually use the filesystem and can let the >> > cache-provider do what it's good at :) >> >> I tried to implement L2 cache before with lift and didnt get very far >> - perhaps i'll give it another go. >> >> My other concern is performance - given a table like: >> >> create table tree_items ( >> id int(11) unsigned not null auto_increment, >> parent_id int(11) unsigned, >> name varchar(20), >> other_content varchar(255), >> primary key (id) >> ); >> >> where parent_id defines the tree structure, im a little worried that >> the queries would be come fairly bloated? I also did some looking >> around to see if there were any examples online of tree structures in >> JPA but alas could not find anything usefull - it appears its quite >> problematic...? >> >> Cheers >> >> Tim >> >> > > > -- > Viktor Klang > Senior Systems Analyst > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
