tag:blogger.com,1999:blog-1973750947775262558.post91590053806630123..comments2011-08-03T05:05:09.699-04:00bill sheltonhttp://www.blogger.com/profile/06624894387927690246noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1973750947775262558.post-29100435708584226372011-08-03T05:05:09.699-04:002011-08-03T05:05:09.699-04:00A <a href="http://www.sitepoint.com/hierarchical-data-database-2/" rel="nofollow">pre-ordered tree </a> is the way to go here.<br /><br />If the nodes need to appear at multiple positions in the tree you can create a link table with the left/right values to allow this.<br /><br />Its ideal for data that changes infrequently as managing the left/right values on the fly is a pita, i tend to keep a parentId column as well and rebuild the left/right values as necessary.Chris Blackwellhttp://www.blogger.com/profile/09541237404886665413noreply@blogger.comtag:blogger.com,1999:blog-1973750947775262558.post-69214396443951672372010-07-18T14:57:40.246-04:002010-07-18T14:57:40.246-04:00I&#39;ve never really looked into the secondary cache at all but now I will. Great post.Sam Farmerhttp://www.blogger.com/profile/17228768778099662772noreply@blogger.com