Hi Jan I had to "neglect" the issue for a while, but now need to resolve it.
You suggested to use an "order by" in the query. A quick follow up questions: What do I have to "order by" when I want the result in the order the nodes appear in the JCR tree? So far (Mag 4.4) this worked perfectly... and as I said: When cooking up a custom NodeUtil class which uses ArrayList instead of HashSet, it also works as expected. As far as I can tell there is no chance of duplicates because there is a method checking for them. I'll check the behavior on Mag 4.5.7 today. If still there I'll create an issue. Cheers, Will On 26.11.2012, at 10:45, Jan Haderka (via Magnolia Forums) wrote: > IIRC there is option to enforce sorting by certain param, but by default > there is not sorting set so there is no guarantee of order. Do you get wrong > order also when you set sorting on? IF yes, then it is definitively bug and > should be logged as such. > > HTH, > Jan > > -- > Context is everything: > http://forum.magnolia-cms.com/forum/thread.html?threadId=aff7b09a-169e-4df7-ba78-5d2e0da2f2d4 > > > ---------------------------------------------------------------- > For list details, see http://www.magnolia-cms.com/community/mailing-lists.html > Alternatively, use our forums: http://forum.magnolia-cms.com/ > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
