Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Positioning Tree Elements #12

Closed
brendon opened this Issue Feb 12, 2010 · 4 comments

Comments

Projects
None yet
2 participants
Contributor

brendon commented Feb 12, 2010

Hi there, I was just wondering what you'd recommend for ordering of the tree elements. nested set allows you to order the items inherently but ancestry doesn't seem to allow this. Should I go back to using acts_as_list along with ancestry? (I used to use that and acts_as_tree).

I certainly like having a separate position column and tree column. I've had major corruption issues with awesome_nested_set where I think it can't handle two people updating the tree near the same time. I'm hoping ancestry has built in capability to handle this problem?

Thanks heaps for your time :)

Brendon

Contributor

brendon commented Feb 12, 2010

Sorry I just read the positioning post someone else put in here. Makes sense to me :)

Owner

stefankroes commented Feb 14, 2010

Maybe I should add something about this to the readme

Contributor

brendon commented Feb 14, 2010

Hehe could be a good idea. I always forget to read the closed and unread issues for some reason :)

Owner

stefankroes commented Feb 27, 2010

added the option to pass an order to arrange for Ruby 1.9 and later. Before that hashes can't be ordered at all.

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment