cayenne-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Razumovsky <razumovsky.and...@gmail.com>
Subject Re: svn commit: r901627 - in /cayenne/main/trunk: docs/doc/src/main/resources/ framework/cayenne-jdk1.5-unpublished/src/main/java/org/apache/cayenne/exp/parser/ framework/cayenne-jdk1.5-unpublished/src/main/jjtree/org/apache/cayenne/ejbql/ framework/
Date Thu, 21 Jan 2010 21:19:06 GMT
I've always thought of EJBQL as of sort of OOP-analogue of SQL. So while
those thinks look logical and work in SQL, why shouldn't they in EJBQL..
So I'm not fully convinced, but if you wish (?), I'll revert that change

2010/1/21 Andrus Adamchik <andrus@objectstyle.org>

>
> On Jan 21, 2010, at 10:38 PM, Andrey Razumovsky wrote:
>
>  So, following specification, this cannot be performed anyhow?
>>
>
> No. But the idea I guess is that pattern is not another column value. It is
> always a literal.
>
>
>
>> I agree subselects in LIKE is not good, then maybe let's change that to
>> input_parameter() | string_literal() | functions_returning_strings() ?
>> Specification does not say what to do if right part is not input parameter
>> or string literal. So is it really bad if we do more than specification
>> says?
>>
>
> I think it doesn't buy us much. LIKE is a rather special case IMO, and this
> is reflected in the spec.
>
>
>  Another weird thing is that pattern_value() unlike other expressions is
>> not
>> described in BNF on pages 109-112..
>>
>
> True. It is described in the text only. The EJBQL BNF is rather sketchy in
> some parts.
>
> Andrus
>
>


-- 
Andrey

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message