db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1438) Text written by SQLException.toString differs between client and embedded driver
Date Wed, 19 Jul 2006 16:36:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1438?page=all ]

David Van Couvering updated DERBY-1438:

    Attachment: DERBY-1438-rev2.diff

This attachment includes all updates to master files.  It is a comment on master-based testing
that a one-line change to source results in a 1MB overall patch because of master file changes.

I tried to scan all the diffs but there was a lot to read.  I did a couple of sanity tests
to increase my confidence that I didn't miss anything:

- I verified that the number of lines added was exactly equal to the number of lines removed
- I verified that if I filtered out "java.sql.SQLException" and "SQL Exception" from the master
file diffs, there was nothing else in there

Reviews appreciated.  I'm running derbyall again since a lot of changes have come in since
my last run.  If it passes, I"ll check it in tomorrow barring any review comments.


svn status output:

M      java/engine/org/apache/derby/impl/jdbc/EmbedSQLException.java
M      java/testing/org/apache/derbyTesting/functionTests/master/iepnegativetests_ES.out
M      java/testing/org/apache/derbyTesting/functionTests/master/statementJdbc30.out
M      java/testing/org/apache/derbyTesting/functionTests/master/parameterMapping.out
M      java/testing/org/apache/derbyTesting/functionTests/master/compressTable.out
M      java/testing/org/apache/derbyTesting/functionTests/master/importExportThruIJ.out
M      java/testing/org/apache/derbyTesting/functionTests/master/nestedCommit.out
M      java/testing/org/apache/derbyTesting/functionTests/master/TransactionTable.out
M      java/testing/org/apache/derbyTesting/functionTests/master/procedure.out
M      java/testing/org/apache/derbyTesting/functionTests/master/ieptests.out
M      java/testing/org/apache/derbyTesting/functionTests/master/iepnegativetests.out
M      java/testing/org/apache/derbyTesting/functionTests/master/streamingColumn.out
M      java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/importExport.out
M      java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/ieptests.out
M      java/testing/org/apache/derbyTesting/functionTests/master/outparams.out
M      java/testing/org/apache/derbyTesting/functionTests/master/releaseCompileLocks.out
M      java/testing/org/apache/derbyTesting/functionTests/master/statementJdbc20.out

> 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:
>         Environment: Sun JDK 1.5
>            Reporter: Olav Sandstaa
>         Assigned To: David Van Couvering
>            Priority: Trivial
>         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


View raw message