Gil Portenseigne commented on OFBIZ-10195:

Hi Taher,
{quote}Putting the new attribute on the field level instead
that was my first idea, but i wondered the use of such attribute in non-search 
fields... So i choose to have it dedicated on search fields. Even if it 
generated more code lines and redundancy...

What is the best to prioritize ? Avoid code redundancy or having dedicated 
attribute that belongs only to search field-types.


For the renaming parts, i'm ok with it :)

Thanks Again

> Add the ability in performFind service to set OR search criteria
> ----------------------------------------------------------------
>                 Key: OFBIZ-10195
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10195
>             Project: OFBiz
>          Issue Type: Improvement
>            Reporter: Gil Portenseigne
>            Assignee: Gil Portenseigne
>            Priority: Minor
>             Fix For: Upcoming Branch
>         Attachments: OFBIZ-10195.patch, OFBIZ-10195.patch
> When using performFind service for advanced entity search, we can meet the 
> need to have search criteria that do not intersect between them, but make the 
> union of the condition.
> To realize this improvement we propose to set a new suffix _grp.
> Thus using :
> <field name="field1"><text-find/></field>
> <field name="field1_grp"><hidden value="unionKey"/></field>
> <field name="field2"><text-find/></field>
> <field name="field2_grp"><hidden value="unionKey"/></field>
> Then the two search fields criteria will be unioned during the search by the 
> OR operator.
> Several different keys can be used for several different unioned condition.

This message was sent by Atlassian JIRA

Reply via email to