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 DB5DF10A6E for ; Mon, 14 Oct 2013 19:40:52 +0000 (UTC) Received: (qmail 69715 invoked by uid 500); 14 Oct 2013 19:40:45 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 69482 invoked by uid 500); 14 Oct 2013 19:40:42 -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 69462 invoked by uid 99); 14 Oct 2013 19:40:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Oct 2013 19:40:42 +0000 Date: Mon, 14 Oct 2013 19:40:42 +0000 (UTC) From: "Kim Haase (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DERBY-6116) Confusing description of limitation on user-defined aggregate names. 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-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase updated DERBY-6116: ----------------------------- Issue & fix info: Patch Available > Confusing description of limitation on user-defined aggregate names. > -------------------------------------------------------------------- > > Key: DERBY-6116 > URL: https://issues.apache.org/jira/browse/DERBY-6116 > Project: Derby > Issue Type: Bug > Components: Documentation > Affects Versions: 10.10.1.1 > Reporter: Rick Hillegas > Assignee: Kim Haase > Labels: derby_triage10_11 > Attachments: DERBY-6116.diff, rrefsqljcreateaggregate.html > > > The Reference Manual section titled "CREATE DERBY AGGREGATE statement" makes the following ambiguous claim: > "An unqualified UDA name may not be the name of an aggregate defined in part 2 of the SQL Standard, section 10.9" > The term "unqualified UDA name" is supposed to mean the name of the UDA without any schema name. So if the full, schema qualified name of the UDA is MYSCHEMA.FOO, then FOO may not be a SQL Standard aggregate name like MAX, MIN, ANY, etc.. > This was not clear during buddy-testing of UDAs. From the wording in the Reference Manual, the buddy-tester expected to be able to create an aggregate called APP.ANY. -- This message was sent by Atlassian JIRA (v6.1#6144)