[dna-issues] [JBoss JIRA] Resolved: (DNA-543) Add support for JCR-SQL2
Randall Hauch (JIRA)
jira-events at lists.jboss.org
Sat Oct 24 10:28:05 EDT 2009
[ https://jira.jboss.org/jira/browse/DNA-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randall Hauch resolved DNA-543.
-------------------------------
Resolution: Done
The full support of the language was added, with several improvements.
The "IN" clause is supported as an additional DynamicOperand in the WHERE criteria, making it easier to specify a set of possible/allowed values for a property than ORing a Comparison for each of the criteria. For example, a query may use "... WHERE ... [foo:bar] IN ('value 1','value2','value3') ...", which is far easier than "... WHERE ... (([foo:bar] = 'value 1') OR ([foo:bar] = 'value 2') OR ([foo:bar] = 'value 2')) ...".
Two additional DynamicOperand functions are also added. The "DEPTH(<selectorName>)" function can be used to easily obtain the depth of a particular node, and makes it easy to constraint the query to return nodes within a depth range. The "PATH(<selectorName>)" function similarly obtains the path of the node, making it easy to constrain the query to return paths matching patterns.
> Add support for JCR-SQL2
> ------------------------
>
> Key: DNA-543
> URL: https://jira.jboss.org/jira/browse/DNA-543
> Project: DNA
> Issue Type: Feature Request
> Components: Graph, JCR
> Affects Versions: 0.6
> Reporter: Randall Hauch
> Assignee: Randall Hauch
> Fix For: 0.7
>
>
> Add support for querying graphs using the JCR-SQL2 query language defined by the JCR 2.0 specification.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the dna-issues
mailing list