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

Jørgen Løland updated DERBY-1828:
---------------------------------

    Attachment: releaseNote.html

I am uncertain about this release note, so it would be really great if someone 
reviewed it.

Release note attempt:
---------------------------------------
Summary of Change
Most authorization failures have new error codes.

Symptoms Seen by Applications Affected by Change
In the previous release, authorization failures had error codes 2850x and 
04501. In this release, most of these errors have new error codes. The code 
changes are: 04501, 2850H, 2850I and 2850J are now 08004. 28506-2850G are now 
42500-4250A, 28501 is now 4250B, 28503-28505 are now 4250C-4250E. Only the 
error codes have been changed; error messages are not affected.

Incompatibilities with Previous Release
Applications that rely on authorization error codes may fail.

Rationale for Change
The old error codes violated the SQL standard. The new error codes are correct.

Application Changes Required
Applications that rely on authorization error codes must be recoded to expect 
the new codes. 


> 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
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY-1828-1.diff, DERBY-1828-1.stat, DERBY-1828-2.diff, 
> DERBY-1828-2.stat, DERBY-1828-2indent.diff, releaseNote.html
>
>
> 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.

Reply via email to