Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 68909 invoked from network); 19 Apr 2007 18:30:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Apr 2007 18:30:37 -0000 Received: (qmail 17466 invoked by uid 500); 19 Apr 2007 18:30:43 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 17288 invoked by uid 500); 19 Apr 2007 18:30:42 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 17279 invoked by uid 99); 19 Apr 2007 18:30:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Apr 2007 11:30:42 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Apr 2007 11:30:35 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 8A26A714069 for ; Thu, 19 Apr 2007 11:30:15 -0700 (PDT) Message-ID: <7431816.1177007415562.JavaMail.jira@brutus> Date: Thu, 19 Apr 2007 11:30:15 -0700 (PDT) From: "Daniel John Debrunner (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-1828) Access rule violations should use a SQL state starting with '42' according to the SQL standard. In-Reply-To: <4552902.1157662882836.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-1828?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490130 ]=20 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).=20 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 w= hy class 28 was special cased in the spec. > Access rule violations should use a SQL state starting with '42' accordin= g 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=C3=B8rgen L=C3=B8land > > 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 acc= ess rule violation, > JDBC 4.0 maps '42' to SQLSyntaxErrorException which seems wrong for an ac= cess rule. > Message thread: > http://mail-archives.apache.org/mod_mbox/db-derby-dev/200609.mbox/%3c4500= 4A04.5080002@apache.org%3e --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.