title: Best way of representing hierarchical tasks/sub-tasks (MySQL/PHP)
body: <p>I am making a simple todo app (Laravel4/MySQL) and it needs the ability to make tasks and subtasks (limiting it to max. 3 levels)</p>
  
  <p>I was checking out Nested-Set implementations for Laravel <a href="https://cartalyst.com/manual/nested-sets/usage/basic" rel="nofollow">here</a> and <a href="https://github.com/etrepat/baum" rel="nofollow">here</a>. Is it an overkill for my requirement? </p>
  
  <p>I'm guessing nested-sets saves hierarchy data globally (against say, a per-user or per-project basis) and are better for items like a multilevel menu with a limited number of items. 
  What is the best implementation for my case, where hundreds of users would have a multitude of projects and each having hundreds of multilevel tasks/sub-tasks? Would there be unnecessary traversals/overheads if I implement nested-sets for my case? </p>