> Am 24.06.2015 um 20:28 schrieb Ruggentaler, JR :
>
> Yes and no. We use EOGenerate (gap pattern) and ERXKey in our apps to take
> advantage of the nice Wonder features and eclipse code completion. The
> ERXKey.between() method calls ERXQ.between() which builds and returns a
> ERXAndQualifier
Yes and no. We use EOGenerate (gap pattern) and ERXKey in our apps to take
advantage of the nice Wonder features and eclipse code completion. The
ERXKey.between() method calls ERXQ.between() which builds and returns a
ERXAndQualifier.
Both ERXKey.between() and ERXQ.between() are declared to ret
Does ERXBetweenQualifier help?
> On Jun 24, 2015, at 10:53 AM, Ruggentaler, JR
> wrote:
>
> Why does the ERXKey.between() method return a EOQualifier and most of the
> other ERXKey methods return a chain-able ERXQualifier?
>
> I am trying to do something like:
>
> EOQualifier qual = Foo.ST
Why does the ERXKey.between() method return a EOQualifier and most of the other
ERXKey methods return a chain-able ERXQualifier?
I am trying to do something like:
EOQualifier qual = Foo.START_DATE.between(startDate, endDate)
.and(Bar.DATE_DELETED.isNull());
instead of:
EOQualifier qua
Thanks. That is what I did. (That is the way I used to do it, back when I
remembered this stuff better) However, if I want the “new wonder project”
template to work, I will need to install the built wonder frameworks in one of
the directories chuck listed. That is what I had forgotten (this
