jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-155) Query: limited support for the deprecated JCR 1.0 query language Query.SQL
Date Thu, 28 Jun 2012 10:13:42 GMT

    [ https://issues.apache.org/jira/browse/OAK-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402980#comment-13402980

Julian Reschke commented on OAK-155:

Sounds right to me. As far as I recall, if we can map XPath as specified in JCR 1.0, then
we should also be able to map SQL (as per JCR 1.0).

Reminder: given a different query parser we may end up with differences in how invalid queries
are handled; Jackrabbit IMHO is very forgiving when seeing things it doesn't understand.
> Query: limited support for the deprecated JCR 1.0 query language Query.SQL
> --------------------------------------------------------------------------
>                 Key: OAK-155
>                 URL: https://issues.apache.org/jira/browse/OAK-155
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>            Reporter: Thomas Mueller
> Existing applications (as well as the TCK) use the JCR 1.0 query language
> "sql". As far as I know, there are only few differences between JCR 1.0 SQL and JCR 2.0
SQL-2. To make old applications work with Oak, I suggest we provide support JCR 1.0 SQL as
well. An additional advantage is that more of the existing TCK tests can be run.
> I currently don't know if the full JCR 1.0 SQL syntax can be supported (similar to XPath);
if we find supporting certain features is too complicated we will document those limitations

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message