[
https://issues.apache.org/jira/browse/OFBIZ-11701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Malin closed OFBIZ-11701.
---------------------------------
Fix Version/s: Upcoming Branch
Resolution: Done
> 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
> Fix For: Upcoming Branch
>
>
> 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)
