db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Bengtson (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JDO-383) JPOX: issues with the default Unique setting for aggregate queries
Date Wed, 31 May 2006 15:40:30 GMT
     [ http://issues.apache.org/jira/browse/JDO-383?page=all ]
Erik Bengtson resolved JDO-383:

    Resolution: Fixed

fixed in JPOX CVS

> JPOX: issues with the default Unique setting for aggregate queries
> ------------------------------------------------------------------
>          Key: JDO-383
>          URL: http://issues.apache.org/jira/browse/JDO-383
>      Project: JDO
>         Type: Bug

>   Components: tck20
>     Versions: JDO 2 final
>     Reporter: Michael Bouschen
>     Assignee: Erik Bengtson
>     Priority: Minor
>      Fix For: JDO 2 maintenance release 1

> The JDOQL query Unique flag defaults to true for a query with a single result expression
and the result expression is an aggregate (COUNT, MIN, MAX, AVG, SUM).  JPOX calculates the
correct default value for Unique if the result expression is specified w/o any whitespaces
between the aggreagte keyword and the expression in parenthesis: setResult("MIN(budget)").
However, JPOX defaults the Unqiue flag to false, if there is a blank after the aggregate keyword:
setResult("MIN (budget)").
> With the fix of JDO-381 the TCK test class DefaultUnique in package org.apache.jdo.tck.query.result
fails, because I added some test queries having a blank after the aggregate keyword. They
now return a list with the aggregate value instead of the value itself.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message