[creocoder]

https://github.com/c...-set-behavior-2

This is new version of my https://github.com/y...ed-set-behavior

I really hope for feedback.

[Ben]

Did you basically adjust it to yii2's new ActiveRecords, or are there any new concepts?

One thing I didn't like about the original version (although I think it was the only option you had) was the use of a special save() method. I think it's kind of weird that you work with an AR, attach an behavior to it, and all of a sudden can't use its original methods any more. If the new AR design allows to change this, I think it would be a great improvement.

Other nice to have's:
- possibility to store the tree structure in a separate db table. Maybe really one structure table, for data from n other tables (but that would mean to loose FK constraint support).
- there are a few advanced nested set numbering methods available, I think mostly targeting the speed-up of structure changes. The basic method with lft, rgt running from 1 to n*2 when using n data sets has the disadvantage that you need to renumber large portions of the available datasets when changing the tree structure. Other methods try to use ranges, leaving space between lft and rgt for future insertions so you don't have to renumber on every write. Or they use floats instead of integers so that you can always insert a new element (insert between 1 and 2 --> use 1/2. Insert between 1/2 and 1 --> 1/4).

[creocoder]

Ben, on 06 May 2013 - 06:28 AM, said:

Did you basically adjust it to yii2's new ActiveRecords, or are there any new concepts?

All new ActiveRecord concepts used.

Ben, on 06 May 2013 - 06:28 AM, said:

One thing I didn't like about the original version (although I think it was the only option you had) was the use of a special save() method. I think it's kind of weird that you work with an AR, attach an behavior to it, and all of a sudden can't use its original methods any more. If the new AR design allows to change this, I think it would be a great improvement.

New AR design can't allow this. This is php limitation.

Ben, on 06 May 2013 - 06:28 AM, said:

Other nice to have's:
- possibility to store the tree structure in a separate db table. Maybe really one structure table, for data from n other tables (but that would mean to loose FK constraint support).

You can do that with existing behavior.

Ben, on 06 May 2013 - 06:28 AM, said:

- there are a few advanced nested set numbering methods available, I think mostly targeting the speed-up of structure changes. The basic method with lft, rgt running from 1 to n*2 when using n data sets has the disadvantage that you need to renumber large portions of the available datasets when changing the tree structure. Other methods try to use ranges, leaving space between lft and rgt for future insertions so you don't have to renumber on every write. Or they use floats instead of integers so that you can always insert a new element (insert between 1 and 2 --> use 1/2. Insert between 1/2 and 1 --> 1/4).

Better to use another tree type. This is NS confines.

[qiang]

@creocoder: this is great. Could you summarize your feeling about the new AR design on the aspect of developing behaviors, compared with that in 1.1? I'd like to hear this feedback to see if we miss anything.

[creocoder]

@qiang: Thanks. I need to investigate a little more. After that i'll say my opinion.

[jacmoe]

/* extension authoring guidelines discussion split out into this topic: http://www.yiiframew...sion-authoring/ */

[andriusk]

Hello.

Very nice extension. I want to ask, maybe you are going to add functionality of moving subtree to another node as parent?

I got 3000+ records in my tree and when one parent node is removed, I want easily move all its children to new parent.