Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.1.2
-
None
-
None
-
Linux, JRE 1.6.0_07
Description
The attached code demonstrates a situation where a query which specifies an order by node name is returning results in the wrong order.
This seems to be a very specific case, since any of the following stop the problem occuring:
- Removing the NodeType.MIX_VERSIONABLE from the test node type.
- Commenting out the line properties.put("property6", "value6"); ie only using 5 properties instead of 6.
- Removing the where clause from the query (ie using the commented out query instead)
It seems to be something to do with setting the properties on the nodes since the ones that have had properties set seem to be 'moved' to a different place in the result list. Also I tested this with the same node set up using an import of the node data instead and this had the same problem.