I've been told approach doesn't work very well with a tree.



  • Yesterday, I figured out how the php catalog tree works. That was it. https://ru.stackoverflow.com/questions/473815/%D0%BD%D0%B5-%D0%BC%D0%BE%D0%B3%D1%83-%D0%BF%D0%BE%D1%81%D1%82%D1%80%D0%BE%D0%B8%D1%82%D1%8C-%D0%B4%D0%B5%D1%80%D0%B5%D0%B2%D0%BE-%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B9 And yesterday, I learned that this approach outdated rather than replaced it and why?

    It's about the overthrow and storage of the tree itself, not that the php and mysql are outdated.



  • There's a few ways to store trees, one of the most advanced trees I see in the River Bases is Nested Sets


Log in to reply
 


Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2