Reason for the parent_id?

[attilahorvath]

Hi,

I've been evaluating this gem for a project I'm working on and I'm a bit confused about the reliance on a parent_id here. The parent is always obvious by looking at the path and the ltree extension provides all the DB functions needed to work with this so I'm not sure about why it's necessary.

Is this being used to speed up the query performance? Would that be necessary even if I use a GiST index over the ltree?

There is another very similar gem that works fine without this parent ID and I'm trying to decide between these two solutions so I though I'd ask.

Thanks!

[tambakoo]

@attilahorvath did you go ahead with this gem ?