Hi Daniel,
using nested sets AND parent_id's makes the code hard to understand.
You are mixing to different concepts which also doubles potential
error pits.
You've nailed it! Thats what i wanted to say. I can go with both
concepts alone. But mixing them is really strange! Although you could
| marmalade.de
Gesendet: Dienstag, 17. Juli 2012 09:22
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Nested Sets and OXSORT
Hi Daniel,
using nested sets AND parent_id's makes the code hard to understand.
You are mixing to different concepts which also doubles potential error
Hi,
today we discussed the oxcategories-structure.
We are wondering why there is a oxsort field.
As told everywhere, OXID uses nested sets for building the categorytree.
So normaly you don't need a manual sorting-field.
Could you explain why you not just rely on them?
Best Joscha
--
...@lists.oxidforge.org
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Joscha Krug
| marmalade.de
Gesendet: Montag, 16. Juli 2012 17:48
An: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] Nested Sets and OXSORT
Hi,
today we discussed the oxcategories-structure.
We are wondering
Hi All,
2012/7/16 Frank Zunderer frank.zunde...@zunderer.de
i think nested sets are not used for building the categorytree, it’s built
from id/parentid.
And the sorting becomes easier, because every category with oxparent =
'oxrootid' has oxleft=1 at the moment.
Regards,
Björn
--
Ok, seems like OXID is NOT using nested sets?!
The question is more like: Why do we have left+right although we use
ParentID and Sorting?
Isn't that a bit too redundant?
Regards,
Joscha
//-
marmalade.de
Joscha Krug
www.marmalade.de http://www.marmalade.de/
k...@marmalade.de
Hi Maz(vydas,
oxrootid is used for reducing row changing in DB. for example: you
adding new category in first root category, so you updating all oxleft
and oxright after your new category. To limit these updates, Oxid using
oxroot, so only one branch will be affected on category insert or
