By Gijs Van Tulder

Storing Hierarchical Data in a Database, Part 2

By Gijs Van Tulder

Storing Hierarchical Data in a Database

Modified Preorder Tree Traversal

Now, let’s have a look at another method for storing trees. Recursion can be slow, so we would rather not use a recursive function. We’d also like to minimize the number of database queries. Preferably, we’d have just one query for each activity.

We’ll start by laying out our tree in a horizontal way. Start at the root node (‘Food’), and write a 1 to its left. Follow the tree to ‘Fruit’ and write a 2 next to it. In this way, you walk (traverse) along the edges of the tree while writing a number on the left and right side of each node. The last number is written at the right side of the ‘Food’ node. In this image, you can see the whole numbered tree, and a few arrows to indicate the numbering order.


We’ll call these numbers left and right (e.g. the left value of ‘Food’ is 1, the right value is 18). As you can see, these numbers indicate the relationship between each node. Because ‘Red’ has the numbers 3 and 6, it is a descendant of the 1-18 ‘Food’ node. In the same way, we can say that all nodes with left values greater than 2 and right values less than 11, are descendants of 2-11 ‘Fruit’. The tree structure is now stored in the left and right values. This method of walking around the tree and counting nodes is called the ‘modified preorder tree traversal’ algorithm.

Before we continue, let’s see how these values look in our table:


Note that the words ‘left’ and ‘right’ have a special meaning in SQL. Therefore, we’ll have to use ‘lft’ and ‘rgt’ to identify the columns. Also note that we don’t really need the ‘parent’ column anymore. We now have the lft and rgt values to store the tree structure.

Retrieve the Tree

If you want to display the tree using a table with left and right values, you’ll first have to identify the nodes that you want to retrieve. For example, if you want the ‘Fruit’ subtree, you’ll have to select only the nodes with a left value between 2 and 11. In SQL, that would be:


That returns:


Well, there it is: a whole tree in one query. To display this tree like we did our recursive function, we’ll have to add an ORDER BY clause to this query. If you add and delete rows from your table, your table probably won’t be in the right order. We should therefore order the rows by their left value.


The only problem left is the indentation.

To show the tree structure, children should be indented slightly more than their parent. We can do this by keeping a stack of right values. Each time you start with the children of a node, you add the right value of that node to the stack. You know that all children of that node have a right value that is less than the right value of the parent, so by comparing the right value of the current node with the last right node in the stack, you can see if you’re still displaying the children of that parent. When you’re finished displaying a node, you remove its right value from the stack. If you count the elements in the stack, you’ll get the level of the current node.

function display_tree($root) {  
   // retrieve the left and right value of the $root node  
   $result = mysql_query('SELECT lft, rgt FROM tree '.  
                          'WHERE title="'.$root.'";');  
   $row = mysql_fetch_array($result);  
   // start with an empty $right stack  
   $right = array();  
   // now, retrieve all descendants of the $root node  
   $result = mysql_query('SELECT title, lft, rgt FROM tree '.  
                          'WHERE lft BETWEEN '.$row['lft'].' AND '.  
                          $row['rgt'].' ORDER BY lft ASC;');  
   // display each row  
   while ($row = mysql_fetch_array($result)) {  
       // only check stack if there is one  
       if (count($right)>0) {  
           // check if we should remove a node from the stack  
           while ($right[count($right)-1]<$row['rgt']) {  
       // display indented node title  
       echo str_repeat('  ',count($right)).$row['title']."n";  
       // add this node to the stack  
       $right[] = $row['rgt'];  

If you run this code, you’ll get exactly the same tree as with the recursive function discussed above. Our new function will probably be faster: it isn’t recursive and it only uses two queries.

The Path to a Node

With this new algorithm, we’ll also have to find a new way to get the path to a specific node. To get this path, we’ll need a list of all ancestors of that node.

With our new table structure, that really isn’t much work. When you look at, for example, the 4-5 ‘Cherry’ node, you’ll see that the left values of all ancestors are less than 4, while all right values are greater than 5. To get all ancestors, we can use this query:

SELECT title FROM tree WHERE lft < 4 AND rgt > 5 ORDER BY lft ASC;

Note that, just like in our previous query, we have to use an ORDER BY clause to sort the nodes. This query will return:

| title |
| Food |
| Fruit |
| Red |

We now only have to join the rows to get the path to ‘Cherry’.

How Many Descendants

If you give me the left and right values of a node, I can tell you how many descendants it has by using a little math.

As each descendant increments the right value of the node with 2, the number of descendants can be calculated with:

descendants = (right – left - 1) / 2

With this simple formula, I can tell you that the 2-11 ‘Fruit’ node has 4 descendant nodes and that the 8-9 ‘Banana’ node is just a child, not a parent.

Go to page: 1 | 2 | 3
  • ivan malik

    how to create a collapsible menu from items in db ie to show only one level at the time, for example:
    when you click on ‘food’ you get the two items: ‘fruit’ and ‘meat’; then when you click on fruit you should see ‘red’ and ‘yellow’ etc.

  • thank you for this article.I want to create a a portion of website in which I need a tree like hierarchy but
    ithas two levels of depth and childs are multiple. Can you suggest design in RDBMS for it. I need to navigate page only and nothing else with its help

  • Ben Laidler

    Hi Gijs, for the MPTT method, when you are trying to create the indented tree list, you are fetching all nodes with a lft value BETWEEN a parent node’s lft and rght value.

    I believe this would include the parent node itself in the result set (at least in MySQL)? So surely when you are “popping” rght values out of the $right array stack if they have a rght > [last value in $right], none would have a higher rght value than the parent node itself and so all child nodes would be discarded?

  • nuno

    hi, i have a problem

    I have several users and each user have a diferent struture in is information treeview.
    How can a do this.
    I think abaut the problem. Putting the users in the level below the root and below each user put the Hierarchical information acording the need of each user. But i have a little problem. If i have 1000 users, if a add a node in the lowest level of the user number 1, it could be a litle slow, because it need to calculate for the others nodes for each user.

    ———————————————————————- ……
    user1 user2 user3 ……
    ————- ————— ————–…….
    item1 item2 ert1 ert2
    ——- ——- ——– … ———— ……
    a1 a2 b1 b2 w4 rt tyu tre

    Someone have some idea or this algorithm dont work in this situation?

  • Yogesh Kushwaha

    I want to know idea about mlm binary tree. How can they manage membership plan with the help of binary tree structure

  • Rob

    Great article, very simple and powerful. I’m creating a cms and need a way to re-order the categories using move up/move down buttons. I only want to allow re-ordering with categories eg. if ‘fruit’ had an additional sub category ‘green’, red could move down only, yellow could move up or down and green could move up only. How can I evaluate if the node has siblings and if it is the first or last sibling.
    Also how can I get the first level of children eg using fruit: red and yellow but not cherry or banana.
    Any help appreciated.

  • I remember Joe Celko explaining this about 20 years ago but I never understood what the heck the left and the right meant until now. You explanation and diagram made the light go on.

Get the latest in Front-end, once a week, for free.