[
https://issues.apache.org/jira/browse/DERBY-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-2676.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.6.0.0
Assignee: (was: Abhilash T.G)
Thanks for the patch!
Committed revision 762122.
I'm marking the issue as resolved even though the wrong class name is still
used in the reference manual. I believe that generating a new list of error
messages is one of the steps in the release process
(http://wiki.apache.org/db-derby/DerbySnapshotOrRelease) so it will be done by
someone else in a bulk operation later.
Resetting assignee. Could one of the JIRA superusers add Hiranya to the
derby-developers group so that the issue could be assigned to him?
> Class name "com.ibm.db2j.aggregates.Aggregator" refered in error message is
> no longer correct
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-2676
> URL: https://issues.apache.org/jira/browse/DERBY-2676
> Project: Derby
> Issue Type: Bug
> Components: Documentation, Newcomer, SQL
> Reporter: Tomohito Nakayama
> Priority: Trivial
> Fix For: 10.6.0.0
>
> Attachments: DERBY-2676.patch
>
>
> Error message for 42Y32 refers com.ibm.db2j.aggregates.Aggregator is as next.
> > 42Y32 Aggregator class '<className>' for aggregate '<aggregateName>' on
> > type <type> does not implement com.ibm.db2j.aggregates.Aggregator.
> Reading
> org.apache.derby.impl.sql.compile.AggregateNode#checkAggregatorClassName,
> however, the current fully qualified name for the class is
> org.apache.derby.iapi.sql.execute.ExecAggregator.
> Same problem exists in reference manual also.
> http://db.apache.org/derby/docs/dev/ref/rrefexcept71493.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
