You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/07/08 15:36:00 UTC
[jira] [Commented] (OFBIZ-12663) Allow DynamicView use in standard performFind services
[ https://issues.apache.org/jira/browse/OFBIZ-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564331#comment-17564331 ]
ASF subversion and git services commented on OFBIZ-12663:
---------------------------------------------------------
Commit f158685cebbd5c11eeb3f0333fd5a8ed132208e3 in ofbiz-framework's branch refs/heads/release22.01 from Nicolas Malin
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=f158685ceb ]
Improved: Allow DynamicView use in standard performFind services (OFBIZ-12663)
Extend standard find services (prepareFind, executeFind and performFind) to use a built dynamicView instead of just an entityName.
With this, you can prepare a dedicated dynamicView and call the performFind with on result a database optimisation.
Thanks to Leila Mekika for this proposal and patch
> Allow DynamicView use in standard performFind services
> ------------------------------------------------------
>
> Key: OFBIZ-12663
> URL: https://issues.apache.org/jira/browse/OFBIZ-12663
> Project: OFBiz
> Issue Type: Improvement
> Components: framework/common
> Affects Versions: Upcoming Branch
> Reporter: Leila Mekika
> Priority: Major
> Attachments: OFBIZ-12663.patch
>
>
> This is a proposition to extend the use of standard find services (prepareFind, executeFind and performFind) to dynamicView.
> It can help to have performFind services (such has performFindParty) that use the same standard service
> To describe quickly, it adds dynamicViewEntity as an optional parameter of prepareFind, executeFind and performFind services and adapt the query accordingly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)