db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3610) Confusing error message when granting execute privilege
Date Tue, 07 Apr 2009 23:25:13 GMT

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

Dag H. Wanvik commented on DERBY-3610:

To be clear, I think it is good to reuse the SQL state (42Y03), but
introduce two new messages as you suggest (i.e. no new state).

As for keywords in messages, all caps is probably advisable.  Still, in this
case, "function" and "procedure" are actually used as concepts more
than referring to the actual keyword (although that distinction is
often blurry it is fairly clear here), so providing a version of the
error messages that would allow these terms to be translated is good for

So, +1 to two new messages reusing the old SQL state.

> 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
>            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