db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-6116) Confusing description of limitation on user-defined aggregate names.
Date Mon, 14 Oct 2013 20:31:42 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kim Haase resolved DERBY-6116.

          Resolution: Fixed
       Fix Version/s:
    Issue & fix info:   (was: Patch Available)

Thanks, Rick -- that was quick!

Committed patch DERBY-6116.diff to documentation trunk at revision 1532053. 
Merged to 10.10 doc branch at revision 1532072.

> 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:
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>              Labels: derby_triage10_11
>             Fix For:,
>         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

View raw message