You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Thomas Müller <th...@day.com> on 2009/09/25 09:57:58 UTC

Re: PropertyValue constraint fails with implicit selectorName using SQL2

Hi,

This looks like a bug in the SQL-2 parser, could you create a new issue?
Thanks for reporting!

Regards,
Thomas


On Thu, Sep 24, 2009 at 3:55 PM, Philipp Bunge <bu...@crimson.ch> wrote:
> Hi All
>
> I'm not sure if this is a bug or if I'm not reading the spec right.
>
> The following query works:
>
> SELECT * FROM [my:thing] AS thing WHERE thing.[my:property] = 'abc'
>
> the following doesn't:
>
> SELECT * FROM [my:thing] AS thing WHERE [my:property] = 'abc'
>
> (the "AS thing" is unecessary here, I can leave it out with the same result).
>
> The second query results in an:
> javax.jcr.query.InvalidQueryException: Query:
> SELECT * FROM [my:thing] AS thing WHERE [(*)my:property] = 'abc';
> expected: NOT, (
>
> The spec final draft however states:
>
> PropertyValue ::= [selectorName'.'] propertyName
>    /* If only one selector exists in this query,
>       explicit specification of the selectorName is
>       optional */
>
> Does this look like a bug to you? If so I can post a bug report if you like.
>
> Thanks,
> Philipp
>

Re: PropertyValue constraint fails with implicit selectorName using SQL2

Posted by Thomas Müller <th...@day.com>.
Hi,

Thanks a lot! I fixed the bug in the trunk.

Regards,
Thomas

On Fri, Sep 25, 2009 at 11:09 AM, Philipp Bunge <bu...@crimson.ch> wrote:
> Hi Thomas
>
>> This looks like a bug in the SQL-2 parser, could you create a new issue?
>> Thanks for reporting!
>
> Thanks for confirming. I've filed the bug report.
>
> https://issues.apache.org/jira/browse/JCR-2328
>
> Cheers,
> Philipp
>

Re: PropertyValue constraint fails with implicit selectorName using SQL2

Posted by Philipp Bunge <bu...@crimson.ch>.
Hi Thomas

> This looks like a bug in the SQL-2 parser, could you create a new issue?
> Thanks for reporting!

Thanks for confirming. I've filed the bug report.

https://issues.apache.org/jira/browse/JCR-2328

Cheers,
Philipp