Hey viktor, I need the tree structure because it's for this publishing engine I'm writing. The idea is that you could create a page, and that page can have x number of children, and there children cab have children etc etc
Does that make sense? Perhaps there is a more intuitive way to do this? Cheers Tim Sent from my iPhone On 30 Nov 2008, at 13:29, "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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
