ibatis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sven Boden (JIRA)" <ibatis-...@incubator.apache.org>
Subject [jira] Closed: (IBATIS-150) Requirement and benefit of groupBy attribute is not clear in SQL Maps Dev Guide
Date Sat, 18 Feb 2006 20:47:27 GMT
     [ http://issues.apache.org/jira/browse/IBATIS-150?page=all ]
Sven Boden closed IBATIS-150:

    Fix Version: 2.2.0
     Resolution: Fixed
      Assign To: Sven Boden

OpenOffice document changed. PDF regenerated. The PDF is not yet available on the website,
but can be downloaded at: http://svn.apache.org/repos/asf/ibatis/trunk/java/docs/

> Requirement and benefit of groupBy attribute is not clear in SQL Maps Dev Guide
> -------------------------------------------------------------------------------
>          Key: IBATIS-150
>          URL: http://issues.apache.org/jira/browse/IBATIS-150
>      Project: iBatis for Java
>         Type: Improvement
>   Components: Documentation
>     Reporter: Ersin Er
>     Assignee: Sven Boden
>     Priority: Minor
>      Fix For: 2.2.0
>  Attachments: iBATIS-SqlMaps-2.sxw
> The example on page 28 of SQL Maps Developer Guide uses "groupBy" attribute's requirement
and benefit in the SQLMap XML file. The requirement and benefit of this attribute is not clear.
There are two main reasons for this issue:
> 1) The SQL statement given as an example also uses groupBy (which is really not related
to the one usen as an XML attribute.)
> 2) The groupBy attribute's value is given as the name of the DB table column which also
same as the Java class' preperty name.
> Solution:
> 1) A simpler query may be provided so that groupBy attributes requirement and benefits
becomes clearer.
> 2) Column name and property name may be selected to be different so that it becomes clear
that groupBy attribute takes a property name as the value.

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