[
https://issues.apache.org/jira/browse/OFBIZ-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Malin closed OFBIZ-4374.
--------------------------------
Resolution: Implemented
Fix Version/s: Upcoming Branch
With some lucky the patch has been applied on trunk without error.
I commit it on trunk at revision 1655499 with code reformatting and junit test.
With the difficulty to test, I create a new test-suite performfindtests with
five junit :
* testPerformFindConditionFieldEquals
* testPerformFindConditionFieldLike
* testPerformFindConditionDistinct
* testPerformFindFilterByDate
* testPerformFindFilterByDateWithDedicateDateField
I also improve TestNodeMember with two fields extendFromDate and extendThruDate
to realize filter on it.
Thanks Anne for your issue
> Support filtering on non-std date field names in performFind and prepareFind
> ----------------------------------------------------------------------------
>
> Key: OFBIZ-4374
> URL: https://issues.apache.org/jira/browse/OFBIZ-4374
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: Trunk
> Environment: REV 1152668
> Reporter: Anne Jessel
> Assignee: Nicolas Malin
> Priority: Trivial
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-4374_FilterNonStdDateFieldNames.patch,
> OFBIZ-4374_FilterNonStdDateFieldNames.patch
>
>
> I had a need to filter by date ranges for entities that didn't follow the
> standard fromDate and thruDate field-naming pattern. I therefore enhanced
> prepareFind and performFind services so they could be passed the names of the
> fields to use in place of fromDate and thruDate when the filterByDate option
> was chosen. Thought this might be useful to others, even though it isn't
> currently used in OOTB code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
