[
https://issues.apache.org/jira/browse/JDO-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972584#action_12972584
]
Andy Jefferson commented on JDO-643:
------------------------------------
If the datastore indeed does evaluate it as double (equivalent) then your
comment makes sense.
JPA doesn't allow specification of candidate instances and hence allow
in-memory evaluation whereas JDO does. That is one case where avg(BigInteger)
returning BigDecimal makes sense. If it's the only case then it likely
shouldn't effect a change to the general rule.
> avg return type
> ---------------
>
> Key: JDO-643
> URL: https://issues.apache.org/jira/browse/JDO-643
> Project: JDO
> Issue Type: Bug
> Components: specification
> Affects Versions: JDO 2 maintenance release 2
> Reporter: Guido Anzuoni
> Assignee: Michael Bouschen
> Fix For: JDO 3 maintenance release 1
>
> Attachments: JDO-643.patch
>
>
> Aggregate type specification at page 175 claims that avg(expression) return
> type is the same of the enclosed expression.
> This is wrong from a strictly mathematical point of view.
> In fact, if you select an avg on an int field member the result is truncated.
> The result type should always be double.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
