db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3610) Confusing error message when granting execute privilege
Date Wed, 08 Apr 2009 08:36:12 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696945#action_12696945

Knut Anders Hatlen commented on DERBY-3610:

Adding 42Y03.S.0 and 42Y03.S.1 won't affect those who already use 42Y03, as the three message
ids are different. For consistency though, it may make sense to rename the original 42Y03
message to 42Y03.S.X so that we have

42Y03.S.0 - {0} is not recognized as a function or a procedure
42Y03.S.1 - {0} is not recognized as a procedure
42Y03.S.2 - {0} is not recognized as a function

The constant SQLState.LANG_NO_SUCH_METHOD_ALIAS and the <name> tag for that message
in messages.xml will have to be updated.

> Confusing error message when granting execute privilege
> -------------------------------------------------------
>                 Key: DERBY-3610
>                 URL: https://issues.apache.org/jira/browse/DERBY-3610
>             Project: Derby
>          Issue Type: Improvement
>          Components: Newcomer, SQL
>            Reporter: Dag H. Wanvik
>            Assignee: Hiranya Jayathilaka
>            Priority: Trivial
>         Attachments: DERBY-3610.patch
> When the wrong keyword is used in a grant execute privilege statement, the error message
> leads one the believe the identifier is neither a procedure or a function, when in deed
it is one of the two.
> > create function bc(i int) returns int language java parameter style java external
name 'java.lang.Integer.bitCount' no sql;
> > grant execute on procedure bc to foo;
> ERROR 42Y03: 'BC' is not recognized as a function or procedure.
> > grant execute on function bc to foo;
> (works)
> The reason is that the error message is generic. It would be better to have an error
message for each case.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message