Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cayenne.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Subject: Re: Variations of 'like'
From: Andrus Adamchik <andrus@objectstyle.org>
In-Reply-To: 
 <CAA-upzqPFUWsVeG28VR-Yqv6GANP0BtLYAXW4q7W_GSzzjC7Rg@mail.gmail.com>
Date: Fri, 21 Nov 2014 18:02:31 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <1C50C7D9-B17F-429B-9A81-53268B73702E@objectstyle.org>
References: <1094EEAA-6205-4FAB-B789-E460A3078E4F@objectstyle.org>
 <CAA-upzpKQEnTKNrdhSQcBbiXGwEgrMLN5JPssQqCFhMgq=Z4gg@mail.gmail.com>
 <D7956056-432E-4D78-850F-A0C54BFDB061@objectstyle.org>
 <CAA-upzqPFUWsVeG28VR-Yqv6GANP0BtLYAXW4q7W_GSzzjC7Rg@mail.gmail.com>
To: dev@cayenne.apache.org

enum also makes it needlessly verbose :-/=20

But yeah, I take your point.=20


> On Nov 21, 2014, at 5:56 PM, Michael Gentry <mgentry@masslight.net> =
wrote:
>=20
> I'd avoid true/false for that purpose.  We had the same thing in
> orderings before I changed it to an enum.  I'd specify it in the
> method name or use an enum that makes sense when reading it.
>=20
> mrg
>=20
>=20
> On Fri, Nov 21, 2014 at 9:47 AM, Andrus Adamchik =
<andrus@objectstyle.org> wrote:
>>> So are you thinking something like:
>>> Artist.ARTIST_NAME.contains("Van")?
>>=20
>> yep.
>>=20
>>> Also, what about
>>> case-insensitive?
>>=20
>> Probably as a second true/false argument? I started to dislike the =
look of "likeIgnoreCase" recently :)
>>=20
>> Property.contains(string);
>> Property.contains(string, true);
>> Property.contains(string, false);
>>=20
>>=20
>> Andrus
>>=20
>>=20
>>> On Nov 21, 2014, at 5:33 PM, Michael Gentry <mgentry@masslight.net> =
wrote:
>>>=20
>>> I 'like' this.
>>>=20
>>> So are you thinking something like:
>>> Artist.ARTIST_NAME.contains("Van")?  Also, what about
>>> case-insensitive?
>>>=20
>>> mrg
>>>=20
>>>=20
>>> On Fri, Nov 21, 2014 at 7:19 AM, Andrus Adamchik =
<andrus@objectstyle.org> wrote:
>>>> Another API idea that I just had while analyzing boilerplate code =
of the client Cayenne apps. An argument to Property.like(..) (or second =
argument to ExpressionFactory.likeExp(..)) requires a full pattern to =
match against. So people would often write their own utility code to =
wrap a String in "%" signs. Cayenne can easily take care of this via the =
following methods:
>>>>=20
>>>>=20
>>>> Property.contains(string);
>>>> // same as Property.like("%" + string + "%");
>>>>=20
>>>> Property.startsWith(string);
>>>> // same as Property.like(string + "%");
>>>>=20
>>>> Property.endsWith(string);
>>>> // same as Property.like("%" + string);
>>>>=20
>>>> In addition to saving the user from String concatenation, these new =
methods can do proper symbol escaping, making "like" much safer to use.
>>>>=20
>>>> Andrus
>>>=20
>>=20
>=20