db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1828) Access rule violations should use a SQL state starting with '42' according to the SQL standard.
Date Thu, 19 Apr 2007 18:30:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490130
] 

Daniel John Debrunner commented on DERBY-1828:
----------------------------------------------

Dag:

> The class "28" seems correct for failure to establish a connection
> when checking credentials, cf. its usage in section 17.1 Connect
> statement (SQL 2003). 

Why?

The only use for class 28 is for "invalid authorization specification", all the uses of it
in the SQL specification are for the case when the *format* of the user identifier is invalid,
not for when the authorization fails.

I did raise this issue to the expert group for JDBC 4, I never understood why class 28 was
special cased in the spec.



> Access rule violations should use a SQL state starting with '42' according to the SQL
standard.
> -----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1828
>                 URL: https://issues.apache.org/jira/browse/DERBY-1828
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.2.1.6, 10.3.0.0
>            Reporter: Daniel John Debrunner
>         Assigned To: Jørgen Løland
>
> The SQL standard says that SQL State '42' is for "syntax error or access
> rule violation" (section 23.1).
> There is a question of what JDBC 4.0 exception should be thrown for a access rule violation,
> JDBC 4.0 maps '42' to SQLSyntaxErrorException which seems wrong for an access rule.
> Message thread:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200609.mbox/%3c45004A04.5080002@apache.org%3e

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


Mime
View raw message