jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2282) SQL2 parser must not infer type for UncastLiteral from static analysis
Date Mon, 31 Aug 2009 09:40:32 GMT

     [ https://issues.apache.org/jira/browse/JCR-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Marcel Reutegger updated JCR-2282:

       Resolution: Fixed
    Fix Version/s: 2.0.0
           Status: Resolved  (was: Patch Available)

The JSR 283 EG decided to relax the relevant spec section. That is, an implementation is not
forced to interpret the literal as a string in this context.

Removed unused method Parser.getUncastLiteralSpecCompliant() in spi-commons in revision: 809524

> SQL2 parser must not infer type for UncastLiteral from static analysis
> ----------------------------------------------------------------------
>                 Key: JCR-2282
>                 URL: https://issues.apache.org/jira/browse/JCR-2282
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr-tests, jackrabbit-spi-commons
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 2.0.0
> The spec says:
> "An UncastLiteral is always interpreted as a Value of property type STRING. A CastLiteral,
on the other hand, is interpreted as the string form of a Value of the PropertyType indicated."
> There are also two test cases in NodeNameTest that need to be fixed accordingly: testLongLiteral
and testBooleanLiteral

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message