[jira] [Commented] (OFBIZ-11701) getAssociatedPriceRulesConds service return huge result

[Nicolas Malin (Jira)]

    [ https://issues.apache.org/jira/browse/OFBIZ-11701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17106334#comment-17106334 ]

ASF subversion and git services commented on OFBIZ-11701:
---------------------------------------------------------

Commit a6cfaf87320dab2492502bc27d2c4007aab62b94 in ofbiz-framework's branch refs/heads/trunk from Nicolas Malin
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=a6cfaf8 ]

Improved: getAssociatedPriceRulesConds service return huge result

(OFBIZ-11701)

The service getAssociatedPriceRulesConds return some element to help the selection on product prise rule condition screen.
The problem: all query to resolve element are realized without filter :
     from("Product").queryList()

On big database, a call on this service generate a server saturation (load 1 Million product to a dropdown, isn't logical)
To keep the benefit of this service as example to implement a custom service with filter, I introduce a limit range to 200. For much more it's better to improve the screen with a lookup.

I also simplify the list generation to homogenize and help the reader.

> getAssociatedPriceRulesConds service return huge result
> -------------------------------------------------------
>
>                 Key: OFBIZ-11701
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11701
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: product
>    Affects Versions: Trunk
>            Reporter: Nicolas Malin
>            Assignee: Nicolas Malin
>            Priority: Minor
>
> The service getAssociatedPriceRulesConds return some element to help the selection on product prise rule condition screen.
> The problem: all query to resolve element are realized without filter :
>  {code}from("Product").queryList(){code}
> On big database, a call on this service generate a server saturation (load 1 Million product to a dropdown, isn't logical)
> To keep the benefit of this service as example to implement a custom service with filter, I introduce a limit range to 200. For much more it's better to improve the screen with a lookup.

--
This message was sent by Atlassian Jira
(v8.3.4#803005)