[
https://issues.apache.org/jira/browse/OFBIZ-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372733#comment-14372733
]
Rishi Solanki commented on OFBIZ-5701:
--------------------------------------
[~kieuanhvu]: Picked this one but could not understand what you wants to say,
could you please explain it one more time in some other way which should be
really easier to understand (may be you can use some example records to
explain). From your last comment it looks like not setting the setDistinct will
give you some expected results then what is the need to patch you have provided.
In short if you could help to understand the problem better then we can help.
Also if you are able to achieve your expected results by setting and not
setting the distinct value then this should not be bug. So if no problem then
this should be consider as invalid and recommending to close as invalid.
Please provide more details if this is an valid issue in GenericDAO or it is
something expected in code and not an real issue?
Thanks!
> Bug SQL Count Distinct command in GenericDAO.java
> --------------------------------------------------
>
> Key: OFBIZ-5701
> URL: https://issues.apache.org/jira/browse/OFBIZ-5701
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: Trunk
> Reporter: kieuanhvu
> Attachments: GenericDAO.java.patch, SQLDistinctGenericDAO.diff,
> SQLDistinctGenericDAO.diff
>
>
> I have encounter the problem is: How can ofbiz framework count distinct for
> all selected fields in query function of delegator? Although
> EntityFindOptions.setDistinct(true) and the selected fields are all field,
> the ofbiz framework always count distinct follow only one field.
> I have resolved problem as my attact file
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
