<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Storing hierarchical data in a database Part 2a: Modified preorder tree traversal</title>
	<atom:link href="http://iamcam.wordpress.com/2006/03/24/storing-hierarchical-data-in-a-database-part-2a-modified-preorder-tree-traversal/feed/" rel="self" type="application/rss+xml" />
	<link>http://iamcam.wordpress.com/2006/03/24/storing-hierarchical-data-in-a-database-part-2a-modified-preorder-tree-traversal/</link>
	<description>Cameron Perry's web development blog</description>
	<lastBuildDate>Thu, 22 Oct 2009 21:20:01 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Manju</title>
		<link>http://iamcam.wordpress.com/2006/03/24/storing-hierarchical-data-in-a-database-part-2a-modified-preorder-tree-traversal/#comment-6622</link>
		<dc:creator>Manju</dc:creator>
		<pubDate>Mon, 01 Sep 2008 20:16:02 +0000</pubDate>
		<guid isPermaLink="false">https://iamcam.wordpress.com/2006/03/21/storing-hierarchical-data-in-a-database-part-2a-modified-preorder-tree-traversal/#comment-6622</guid>
		<description>How to insert rows into this table? I mean how to calculate the left and right values? Please let us know.
Thanks,</description>
		<content:encoded><![CDATA[<p>How to insert rows into this table? I mean how to calculate the left and right values? Please let us know.<br />
Thanks,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cameron Perry</title>
		<link>http://iamcam.wordpress.com/2006/03/24/storing-hierarchical-data-in-a-database-part-2a-modified-preorder-tree-traversal/#comment-6620</link>
		<dc:creator>Cameron Perry</dc:creator>
		<pubDate>Fri, 18 Jul 2008 05:03:24 +0000</pubDate>
		<guid isPermaLink="false">https://iamcam.wordpress.com/2006/03/21/storing-hierarchical-data-in-a-database-part-2a-modified-preorder-tree-traversal/#comment-6620</guid>
		<description>Alan,

That third point is interesting and now doubt a fairly simple one to understand, however it seems to me somewhat impractical to use a method such as this when the total depth of the tree is unknown at any given point in the future. I think that is the downside of Chandler&#039;s method - your tables could have an infinite number of columns, each of which are potentially filled with something. It is, however, easy on the eyes and simpler to understand than MPTT, though MPTT still reigns champ in my book.</description>
		<content:encoded><![CDATA[<p>Alan,</p>
<p>That third point is interesting and now doubt a fairly simple one to understand, however it seems to me somewhat impractical to use a method such as this when the total depth of the tree is unknown at any given point in the future. I think that is the downside of Chandler&#8217;s method &#8211; your tables could have an infinite number of columns, each of which are potentially filled with something. It is, however, easy on the eyes and simpler to understand than MPTT, though MPTT still reigns champ in my book.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan deLevie</title>
		<link>http://iamcam.wordpress.com/2006/03/24/storing-hierarchical-data-in-a-database-part-2a-modified-preorder-tree-traversal/#comment-6619</link>
		<dc:creator>Alan deLevie</dc:creator>
		<pubDate>Fri, 18 Jul 2008 00:51:09 +0000</pubDate>
		<guid isPermaLink="false">https://iamcam.wordpress.com/2006/03/21/storing-hierarchical-data-in-a-database-part-2a-modified-preorder-tree-traversal/#comment-6619</guid>
		<description>@Phil:
I recently wrote about a (patented) method for storing hierarchical data in a database which does not require recursion for retrieving the tree as well as altering the tree. It is an improvement (in my opinion) over the path enumeration model. 

Here&#039;s the link: http://www.alandelevie.com/2008/07/12/recursion-less-storage-of-hierarchical-data-in-a-relational-database/</description>
		<content:encoded><![CDATA[<p>@Phil:<br />
I recently wrote about a (patented) method for storing hierarchical data in a database which does not require recursion for retrieving the tree as well as altering the tree. It is an improvement (in my opinion) over the path enumeration model. </p>
<p>Here&#8217;s the link: <a href="http://www.alandelevie.com/2008/07/12/recursion-less-storage-of-hierarchical-data-in-a-relational-database/" rel="nofollow">http://www.alandelevie.com/2008/07/12/recursion-less-storage-of-hierarchical-data-in-a-relational-database/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iamcam &#187; Hierarchical data in a database2b: Modified preorder tree traversal - insertions</title>
		<link>http://iamcam.wordpress.com/2006/03/24/storing-hierarchical-data-in-a-database-part-2a-modified-preorder-tree-traversal/#comment-15</link>
		<dc:creator>iamcam &#187; Hierarchical data in a database2b: Modified preorder tree traversal - insertions</dc:creator>
		<pubDate>Sat, 15 Apr 2006 05:42:43 +0000</pubDate>
		<guid isPermaLink="false">https://iamcam.wordpress.com/2006/03/21/storing-hierarchical-data-in-a-database-part-2a-modified-preorder-tree-traversal/#comment-15</guid>
		<description>[...] Last time I introduced the Modified preorder tree traversal algorithm as a method to store relationships between nodes. This time I&#8217;ll show you how nodes are inserted into the tree. Note that I&#8217;m using MySQL, so you may need to change your queries slightly depending on the DB you&#8217;re using. [...]</description>
		<content:encoded><![CDATA[<p>[...] Last time I introduced the Modified preorder tree traversal algorithm as a method to store relationships between nodes. This time I&#8217;ll show you how nodes are inserted into the tree. Note that I&#8217;m using MySQL, so you may need to change your queries slightly depending on the DB you&#8217;re using. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iamcam</title>
		<link>http://iamcam.wordpress.com/2006/03/24/storing-hierarchical-data-in-a-database-part-2a-modified-preorder-tree-traversal/#comment-12</link>
		<dc:creator>iamcam</dc:creator>
		<pubDate>Sat, 01 Apr 2006 10:00:49 +0000</pubDate>
		<guid isPermaLink="false">https://iamcam.wordpress.com/2006/03/21/storing-hierarchical-data-in-a-database-part-2a-modified-preorder-tree-traversal/#comment-12</guid>
		<description>I&#039;m actually pretty new to the MPTT (blogging as I learn it), but I&#039;ve already figured-out a lot beyond the Sitepoint article.

My next entry will dive a bit deeper where the Sitepoint article began getting shallow - namely in inserting nodes in specific places within the tree. I already pretty much figured-out conceptually how to move a node and its children, which is definitely another entry in and of itself. Here&#039;s a hint: pull-out the node and its children from the DB into an array, delete those rows, do the appropriate math on the nodes to the right of the group, then at the insertion point, do some more math to make room for the node and children, INSERT into your DB the array you pulled out. Just make sure your math makes sense at each step and you should be fine.

I&#039;ll get the next entry up as soon as I can...</description>
		<content:encoded><![CDATA[<p>I&#8217;m actually pretty new to the MPTT (blogging as I learn it), but I&#8217;ve already figured-out a lot beyond the Sitepoint article.</p>
<p>My next entry will dive a bit deeper where the Sitepoint article began getting shallow &#8211; namely in inserting nodes in specific places within the tree. I already pretty much figured-out conceptually how to move a node and its children, which is definitely another entry in and of itself. Here&#8217;s a hint: pull-out the node and its children from the DB into an array, delete those rows, do the appropriate math on the nodes to the right of the group, then at the insertion point, do some more math to make room for the node and children, INSERT into your DB the array you pulled out. Just make sure your math makes sense at each step and you should be fine.</p>
<p>I&#8217;ll get the next entry up as soon as I can&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil</title>
		<link>http://iamcam.wordpress.com/2006/03/24/storing-hierarchical-data-in-a-database-part-2a-modified-preorder-tree-traversal/#comment-11</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Sat, 01 Apr 2006 00:02:49 +0000</pubDate>
		<guid isPermaLink="false">https://iamcam.wordpress.com/2006/03/21/storing-hierarchical-data-in-a-database-part-2a-modified-preorder-tree-traversal/#comment-11</guid>
		<description>I have been working with the Modified Preorder Tree Traversal and have been having difficulties writing an efficient method for moving a node with its child nodes.

I would be grateful if you could publish a method for doing this as my understading of the method is still not quite up to scratch.</description>
		<content:encoded><![CDATA[<p>I have been working with the Modified Preorder Tree Traversal and have been having difficulties writing an efficient method for moving a node with its child nodes.</p>
<p>I would be grateful if you could publish a method for doing this as my understading of the method is still not quite up to scratch.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
