-
1. Re: Query bug in MS3 B3?
rhauch Aug 31, 2012 8:28 AM (in response to chrispoulsen)It's tough to tell offhand if this is a bug in 2.8 or 3.0 without more information. Can you please post:
- the toString() of the QueryObjectModel object? It's not required, but it'd save a bit of time recreating it (especially since the above code doesn't include definitions for some of the values and constants).
- the CND for the custom node type(s) used in the query (including any supertypes)?
Best regards
-
2. Re: Query bug in MS3 B3?
chrispoulsen Aug 31, 2012 8:37 AM (in response to rhauch)Hi,
Here is the QOM.toString():
{code:sql}
JCR-JQOM -> SELECT * FROM [author:textUnit] AS textUnits WHERE (ISCHILDNODE(textUnits,'/author/content/text') AND textUnits.[author:deleted] = CAST('false' AS BOOLEAN)) ORDER BY textUnits.[author:unitId] ASC
AQM -> SELECT * FROM [author:textUnit] AS textUnits WHERE (ISCHILDNODE(textUnits,'/author/content/text') AND textUnits.[author:deleted] = CAST('false' AS BOOLEAN)) ORDER BY textUnits.[author:unitId] ASC LIMIT 10
{code}
The cnd file is attached.
--
Chris
-
author.cnd.zip 658 bytes
-
-
3. Re: Query bug in MS3 B3?
rhauch Aug 31, 2012 9:26 AM (in response to chrispoulsen)Thanks for providing that information. I don't see anything wrong with the query, so it's likely a bug in ModeShape 3's query engine. Can you log this as a bug in our JIRA?