Hi
On 05/09/13 15:17, Kiril Gavrailov wrote:
Well sorry for the spam just realized what the easy solution would be :)
I would just use:
<uri>?_s=somefield=le=blabla;somefield=ge=blabla when I want the exact
result :) and == when I want "like" result
I'm not sure it will give the strict vs like choice, it will be more
like a default comparison of strings, at least in shipped visitors.
FYI, the default JPA visitor will replace '*' with '%' to get wildcard
SQL matches working.
Re your custom JPA visitor: do you reckon some of it can make into the
default JPA visitor ?
Cheers, Sergey
On Thu, Sep 5, 2013 at 5:03 PM, Kiril Gavrailov <[email protected]>wrote:
Hi,
I'm trying to distinguish the "equals" and "like" in my custom
JPAFilterVisitor with which I use the FIQL in order to filter some data
from my db through a rest service.
I was thinking is there a way to introduce a custom condition type so when
I write let's say:
<uri>?_s=somefield==blabla to query my db with "like" and when I write
<uri>?_s=somefield===blabla to query my db for the exact result matching
the exact string "blabla". I saw that in the ConditionType enum there's a
condition type CUSTOM, but I also saw that in the matcher of the search
context there's a regex which does not allow anything custom, but only the
predefined conditions. Any suggestions?
Regards,
Kiril
P.S. My backup plan is to introduce one more QueryParam which precises
whether I want the exact result or I want to query with like, but I really
don't like that solution :)
