Hi,
This works like a charm.
thanks
Hans
Andrey Razumovsky wrote:
It has since 3.0. It's already in beta (and RC1 will likely be this year),
so I advice you to switch.
Otherwise, try
Expression exp = new ASTBetween(new ASTDbPath(pathSpec), value1, value2);
(not sure this is complatible with
It has since 3.0. It's already in beta (and RC1 will likely be this year),
so I advice you to switch.
Otherwise, try
Expression exp = new ASTBetween(new ASTDbPath(pathSpec), value1, value2);
(not sure this is complatible with 2.0)
2009/12/17 Hans Pikkemaat
> but the ExpressionFactory doesnt ha
but the ExpressionFactory doesnt have betweenDbExp.
I'm using version 2 btw
Andrey Razumovsky wrote:
Yeah, for range you'll need betweenDbExp, I just got mistreated with
analogue to paginated queries, which use in
2009/12/17 Hans Pikkemaat
Hi,
I guess this produces the 'IN' operator.
Th
Yeah, for range you'll need betweenDbExp, I just got mistreated with
analogue to paginated queries, which use in
2009/12/17 Hans Pikkemaat
> Hi,
>
> I guess this produces the 'IN' operator.
> This would mean I need to produce all the key values in the range I want to
> retrieve?
>
> Is there not
Hi,
I guess this produces the 'IN' operator.
This would mean I need to produce all the key values in the range I want
to retrieve?
Is there not a betweenDbExp?
tx
Hans
Andrey Razumovsky wrote:
If you're using SelectQuery, Expression.inDbExp() is for you to go. See
http://cayenne.apache.org
If you're using SelectQuery, Expression.inDbExp() is for you to go. See
http://cayenne.apache.org/doc/path-expressions.html
2009/12/17 Hans Pikkemaat
> Hi,
>
> Some paginated mechanisms are based on a persistence layer to be able to
> retrieve records for a range of primary keys.
>
> I know it i
Hi,
Some paginated mechanisms are based on a persistence layer to be able to
retrieve records for a range of primary keys.
I know it is possible to insert the primary key field in the definition
but then I'm also required to populate it
when I create a record. I'm using a sequence generator t
anwsering my own question : "upper" can be used, but the keyword *must* be
in lower case
2009/12/17 Andrey Razumovsky
> So likeIgnoreCase in not supported at all? Is there some workaround?
>
> 2009/12/4 Andrus Adamchik
>
> "likeIgnoreCase" is not valid in EJBQL. Although the error message refer
So likeIgnoreCase in not supported at all? Is there some workaround?
2009/12/4 Andrus Adamchik
> "likeIgnoreCase" is not valid in EJBQL. Although the error message refers
> to something else... strange...
>
>
>
> On Dec 4, 2009, at 4:12 AM, Dave Lamy wrote:
>
> Hey guys--
>>
>> I'm really just
