Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 49B45DECC for ; Wed, 10 Oct 2012 08:03:13 +0000 (UTC) Received: (qmail 3463 invoked by uid 500); 10 Oct 2012 08:03:13 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 2789 invoked by uid 500); 10 Oct 2012 08:03:06 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 2723 invoked by uid 99); 10 Oct 2012 08:03:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2012 08:03:03 +0000 Date: Wed, 10 Oct 2012 08:03:03 +0000 (UTC) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Message-ID: <247182176.18818.1349856183665.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (DERBY-672) Re-enable user defined aggregates MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473075#comment-13473075 ] Knut Anders Hatlen commented on DERBY-672: ------------------------------------------ In UserAggregateDefinition.getJavaClass(): + if ( "byte[]".equals( javaClassName ) ) { javaClassName = "[B"; } Perhaps just return byte[].class directly, so that we get rid of one of the magic strings? And maybe add a short comment saying why byte[] needs special handling. It might also be helpful to add a class-level javadoc comment to LobMode describing what kind of operation it implements. The catch clause in LobMode.toString(Object) loses the stack trace of the original exception. Using "throw new IllegalArgumentException(e)" would produce a better trace, should it ever fail. > Re-enable user defined aggregates > --------------------------------- > > Key: DERBY-672 > URL: https://issues.apache.org/jira/browse/DERBY-672 > Project: Derby > Issue Type: Improvement > Components: SQL > Reporter: Rick Hillegas > Assignee: Rick Hillegas > Attachments: derby-672-01-aa-ddl.diff, derby-672-02-ac-nonDistinct.diff, derby-672-03-aa-distinct.diff, derby-672-03-ab-distinct.diff, derby-672-04-aa-fixJSR169test.diff, derby-672-05-aa-java7testOrderProblem.diff, derby-672-06-aa-grantRevoke.diff, derby-672-07-aa-fixJSR169again.diff, derby-672-08-aa-fixJSR169yetAgain.diff, derby-672-09-ab-udtAggregates.diff, derby-672-10-af-typeBounds.diff, derby-672-11-aa-tests.diff, UserDefinedAggregates.html, UserDefinedAggregates.html > > > Nicolas Dufour in an email thread titled "functions and list" started on November 2, 2005 requests the ability to create user defined aggregates. > This functionality used to be in Cloudscape. It was disabled presumably because it was considered non-standard. However, most of the machinery needed for this feature is still in the code. We should re-enable user defined aggregates after we agree on acceptable syntax. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira