From derby-dev-return-8909-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Wed Oct 05 16:58:59 2005 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 42803 invoked from network); 5 Oct 2005 16:58:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 Oct 2005 16:58:58 -0000 Received: (qmail 81116 invoked by uid 500); 5 Oct 2005 10:53:52 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 81049 invoked by uid 500); 5 Oct 2005 10:53:52 -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: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 81015 invoked by uid 99); 5 Oct 2005 10:53:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Oct 2005 03:53:52 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [222.146.51.83] (HELO smtp.basil.ocn.ne.jp) (222.146.51.83) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Oct 2005 03:53:55 -0700 Received: from [192.168.0.8] (p4150-adsan11honb5-acca.tokyo.ocn.ne.jp [61.214.217.150]) by smtp.basil.ocn.ne.jp (Postfix) with ESMTP id B4AB44877 for ; Wed, 5 Oct 2005 19:53:28 +0900 (JST) Received: from 127.0.0.1 (AVG SMTP 7.0.344 [267.11.10]); Wed, 05 Oct 2005 19:56:42 +0900 Message-ID: <000701c5c99b$782435c0$0800a8c0@Arkat> From: "TomohitoNakayama" To: "Derby Development" References: <906972752.1128508914941.JavaMail.jira@ajax.apache.org> Subject: Re: [jira] Commented: (DERBY-254) SQLStates for SQLExceptions thrown from the client should not be null and should match embedded where possible Date: Wed, 5 Oct 2005 19:56:38 +0900 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; format=flowed; charset=utf-8; reply-type=original X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hello. I think I'm not exactly sure what you told ....... I see exception from client and exception from embed ,which are told in your message ,was very identical in view of engine behavior . What I see is correctly what you told ? Best regards . /* Tomohito Nakayama tomonaka@basil.ocn.ne.jp tomohito@rose.zero.ad.jp tmnk@apache.org Naka http://www5.ocn.ne.jp/~tomohito/TopPage.html */ ----- Original Message ----- From: "Tomohito Nakayama (JIRA)" To: Sent: Wednesday, October 05, 2005 7:41 PM Subject: [jira] Commented: (DERBY-254) SQLStates for SQLExceptions thrown from the client should not be null and should match embedded where possible > [ http://issues.apache.org/jira/browse/DERBY-254?page=comments#action_12331369 ] > > Tomohito Nakayama commented on DERBY-254: > ----------------------------------------- > > Comment moved from wiki > http://wiki.apache.org/db-derby/JDBC_error_messages_and_SQL_States > > Hi, Tomohito. I am dealing with the null SQL states in the client driver as part of my work on internationalizing the messages. I > think it makes a lot of sense for the SQL states to match between network client and embedded client. I noticed, for instance, > test code that did something like: > > if ( client driver is embedded ) > look for SQL State NNNN > else > look for SQL State YYYY > end if > This seems silly. > > What I am doing (we'll see if people have comments on this) is defining a new severity for exceptions thrown by the network > client. Since the exception severity is mapped to the SQLException error code, the application programmer can check the error code > to determine if it's a network client exception. > > The other way they can distinguish is to see what the instance of the class is. It will be an instance of > org.apache.derby.impl.jdbc.EmbedSQLException if it came from the embedded driver, and an instance of > org.apache.derby.client.am.SqlException if it comes from the network client. > > I think we should keep the SQL states (and the error messages) identical where the error is identical between the network client > and the engine. > > Also, I would like to recommend that this discussion be moved to or linked to from the JIRA issue around SQL states -- DERBY-254 > > David VC > > >> SQLStates for SQLExceptions thrown from the client should not be null and should match embedded where possible >> -------------------------------------------------------------------------------------------------------------- >> >> Key: DERBY-254 >> URL: http://issues.apache.org/jira/browse/DERBY-254 >> Project: Derby >> Type: Improvement >> Components: Network Client >> Versions: 10.2.0.0, 10.1.1.0 >> Reporter: Kathey Marsden >> Assignee: David Van Couvering >> Fix For: 10.2.0.0 > >> >> SQLExceptions generated from the client tend to have a null SQLState. An evaluation of the SQLExceptions thrown by the client >> needs to be performed and match embedded where possible. >> If this does not happen before the 10.1 release, it would be good to document that SQLStates in the client will change for >> future releases > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://issues.apache.org/jira/secure/Administrators.jspa > - > For more information on JIRA, see: > http://www.atlassian.com/software/jira > > > > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.344 / Virus Database: 267.11.10/119 - Release Date: 2005/10/04 > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.10/119 - Release Date: 2005/10/04