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 50491D9ED for ; Tue, 4 Sep 2012 16:14:09 +0000 (UTC) Received: (qmail 44727 invoked by uid 500); 4 Sep 2012 16:14:08 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 44701 invoked by uid 500); 4 Sep 2012 16:14:08 -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 44665 invoked by uid 99); 4 Sep 2012 16:14:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2012 16:14:08 +0000 Date: Wed, 5 Sep 2012 03:14:08 +1100 (NCT) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Message-ID: <269272192.33187.1346775248909.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=13447782#comment-13447782 ] Rick Hillegas commented on DERBY-672: ------------------------------------- Hi Mamta, Thanks for thinking about this issue. Right, I have put in logic to prevent user-defined aggregate names from colliding with the names of functions, both builtin functions and user-defined functions. Thinking about this collision is what caused me to stumble across the existing problem with user-defined functions and to log DERBY-5901. Technically, all that has to be prevented is the collision of user-defined aggregate names with the names of 1-arg functions. If someone complains about the over-broad limitation, we can dial it back later on. Thanks. > 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, 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