db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olav Sandstaa (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1438) Text written by SQLException.toString differs between client and embedded driver
Date Thu, 22 Jun 2006 17:07:31 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1438?page=comments#action_12417334 ] 

Olav Sandstaa commented on DERBY-1438:
--------------------------------------

Personally, I prefer the text written by the embedded driver ("SQL Exception:") over the text
written by the client driver ("java.sql.Exception:"), but with the introduction of the SQL
exception hierarchy in Java SE 6 it might be better to use the exact exception name (e.g.
"java.sql.IamSorryThisShouldNotHappenTodayException") which is what I think you get if you
call SQLException.toString() and running with jdk 1.6.


> Text written by SQLException.toString differs between client and embedded driver
> --------------------------------------------------------------------------------
>
>          Key: DERBY-1438
>          URL: http://issues.apache.org/jira/browse/DERBY-1438
>      Project: Derby
>         Type: Improvement

>   Components: JDBC, Newcomer
>     Versions: 10.2.0.0
>  Environment: Sun JDK 1.5
>     Reporter: Olav Sandstaa
>     Assignee: David Van Couvering
>     Priority: Trivial

>
> The first part of the string written by SQLExeption.toString() differs
> between the Derby client driver and the embedded driver. The embedded
> driver writes:
>    SQL Exception: Table/View 'DERBYDB' does not exist.
> while the client driver writes:
>    java.sql.SQLException: Table/View 'DERBYDB' does not exist.
> It would be good if we changed this so the same text is written by
> both drivers. This reduces the difference seen when changing between
> client and embedded Derby and it make it possible to reduce the amount
> of sed-ing or the number of master file variants for some tests.

-- 
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


Mime
View raw message