[
https://issues.apache.org/jira/browse/DERBY-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490215
]
Dag H. Wanvik commented on DERBY-1828:
--------------------------------------
Right, I think this paragraph of section 17.1 threw me off:
:
> 5) If the value of <connection user name>does not conform to the
> implementation-defined restrictions, then an exception condition is
> raised:invalid authorization specification .
but this paragraph is more relevant to credentials failure:
> 11) If the SQL-server rejects the establishment of the SQL-connection,then
> an exception condition is raised: connection exception SQL-server
> rejected establishment of SQL-connection .
so "connection exception" (08) is correct. Sorry for the confusion.
> 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/[EMAIL
> PROTECTED]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
