[
https://issues.apache.org/jira/browse/OAK-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402996#comment-13402996
]
Thomas Mueller commented on OAK-155:
------------------------------------
My current plan is to use a strict parser for both SQL-1 and XPath, so that
unsupported syntax is rejected. For existing applications that no longer work
because of that, we can decide whether we want to support a certain (XPath /
SQL-1) feature in Oak, patching the respective parser, or change the
application. Whatever is less work.
An implementation detail: I plan to use the SQL-2 parser for SQL-1 as well, but
an (internal) switch so that the SQL-1 features are really only supported when
using SQL-1, and rejected when using SQL-2. If this turns out to be a problem
we can still split the parser. As a side effect, SQL-2 syntax is supported for
SQL-1 queries.
But SQL-1 is clearly deprecated, not just within the JCR spec, but also within
Oak. Unlike XPath, which will very likely be supported within Oak for a longer
time, SQL-1 queries should really be converted to SQL-2.
> 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 instead.
--
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
