[
https://issues.apache.org/jira/browse/OFBIZ-9890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265709#comment-16265709
]
Prakhar Kumar commented on OFBIZ-9890:
--------------------------------------
While researching more on this issue I found that findList() method internally
makes use of find() method which actually supports Having condition. But
support for Having condition is not provided in findList() method itself. So
there is a fair chance that this would have been done on purpose. As you have
mentioned we can opt for queryIterator() for including Having condition, so we
can easily get a list by using getCompleteList() method. So, is there any
specific use case for which support for having is required in queryList() as
well. Please share your thoughts on this :)
> Having condition is ignored on queryList() and queryFirst() calls in
> EntityQuery
> --------------------------------------------------------------------------------
>
> Key: OFBIZ-9890
> URL: https://issues.apache.org/jira/browse/OFBIZ-9890
> Project: OFBiz
> Issue Type: Bug
> Components: ALL COMPONENTS
> Affects Versions: Trunk
> Reporter: Gareth Carter
> Assignee: Prakhar Kumar
> Priority: Minor
>
> queryList() and queryFirst() both call internal private query() method. This
> method calls delegator.findList if a normal Entity/ViewEntity is used (not a
> DVE). This has no option to include a having condition and so must opt to use
> queryIterator(). Even queryCount() can use a having condition
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
