You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Olav Sandstaa (JIRA)" <de...@db.apache.org> on 2006/08/10 16:35:15 UTC
[jira] Closed: (DERBY-1438) Text written by SQLException.toString
differs between client and embedded driver
[ http://issues.apache.org/jira/browse/DERBY-1438?page=all ]
Olav Sandstaa closed DERBY-1438.
--------------------------------
I have verified that SQLException.toString() writes the same text in both network client and embedded driver.
Thanks for fixing this, David!
> 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
> Issue Type: Improvement
> Components: JDBC, Newcomer
> Affects Versions: 10.2.0.0
> Environment: Sun JDK 1.5
> Reporter: Olav Sandstaa
> Assigned To: David Van Couvering
> Priority: Trivial
> Fix For: 10.2.0.0
>
> Attachments: DERBY-1438-rev2.diff, DERBY-1438.diff
>
>
> 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