You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/12/17 12:27:00 UTC
[jira] Created: (JCR-2849) Make QueryResult.getNodes() work also
for certain join queries
Make QueryResult.getNodes() work also for certain join queries
--------------------------------------------------------------
Key: JCR-2849
URL: https://issues.apache.org/jira/browse/JCR-2849
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: jackrabbit-core, query
Reporter: Jukka Zitting
Priority: Minor
There are some people who are relying on the pre- JCR-2715 behaviour where a QueryResult.getNodes() will return a node iterator for one selector of a join query even if the JCR 2.0 spec explicitly says that the method should throw a RepositoryException in such cases.
For convenience and to avoid breaking such code, we might want to make the getNodes() method work at least for inner joins (i.e. no null nodes possible) where the SELECT clause contains just a single selector.* entry that identifies the selector that the client is interested in.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2849) Make QueryResult.getNodes() work also
for certain join queries
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-2849.
--------------------------------
Resolution: Won't Fix
Assignee: Jukka Zitting
Resolving as Won't Fix, since it's possible (and even likely) for a join query to return the same node in multiple rows, which makes it difficult to determine what the potential getNodes() call for a join query result should actually return.
> Make QueryResult.getNodes() work also for certain join queries
> --------------------------------------------------------------
>
> Key: JCR-2849
> URL: https://issues.apache.org/jira/browse/JCR-2849
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, query
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
>
> There are some people who are relying on the pre- JCR-2715 behaviour where a QueryResult.getNodes() will return a node iterator for one selector of a join query even if the JCR 2.0 spec explicitly says that the method should throw a RepositoryException in such cases.
> For convenience and to avoid breaking such code, we might want to make the getNodes() method work at least for inner joins (i.e. no null nodes possible) where the SELECT clause contains just a single selector.* entry that identifies the selector that the client is interested in.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.