db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <j...@apache.org>
Subject [jira] Commented: (DERBY-1440) jdk 1.6 client driver omits SQLStates and chained exceptions in error messages
Date Thu, 24 May 2007 20:32:16 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498812
] 

Øystein Grøvlen commented on DERBY-1440:
----------------------------------------

Patch looks good and it solves my issue from DERBY-2496.
+1 to commit.

My only comment is that I did not quite follow the changes in TransactionResourceImpl.wrapInSQLException
so maybe some explanation would be good there.
It seems nextSQLException here represents something different from what is handled by setNextException.
 Maybe it would be better if it was called something else. Also I do not quite understand
the role of seeNextException and the recursive call to wrapInSQLException.




> jdk 1.6 client driver omits SQLStates and chained exceptions in error messages
> ------------------------------------------------------------------------------
>
>                 Key: DERBY-1440
>                 URL: https://issues.apache.org/jira/browse/DERBY-1440
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client, Tools
>    Affects Versions: 10.2.1.6
>         Environment: Sun JDK 1.6
>            Reporter: Olav Sandstaa
>         Assigned To: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: 1440.diff, 1440.stat
>
>
> When running some SQL queries through ij that fails it seems like some
> information about chained exceptions is not presented to the user when
> running with the client driver and jdk 1.6.
> One example SQL that fails (taken from the ieptests.sql):
> =========================================================
> ij> call SYSCS_UTIL.SYSCS_EXPORT_TABLE ('inventory', 'ORDERTABLE' ,
> 'extinout/order.dat', null, null, null) ;
> When running this in ij the following error message is produced:
> Java 1.6 Embedded driver:
> =========================
> ERROR 38000: The exception 'java.sql.SQLSyntaxErrorException: Schema
> 'inventory' does not exist' was thrown while evaluating an expression.
> ERROR 42Y07: Schema 'inventory' does not exist
> Java 1.5 Client driver:
> =======================
> ERROR 38000: The exception 'SQL Exception: Schema 'inventory' does not
> exist' was thrown while evaluating an expression. SQLSTATE: 42Y07:
> Schema 'inventory' does not exist
> Java 1.6 Client driver:
> =======================
> ERROR 38000: The exception 'java.sql.SQLSyntaxErrorException: Schema
> 'inventory' does not exist' was thrown while evaluating an expression.
> The bug (or difference) here is that the client driver when running
> with jdk 1.6 does not print the chained exception and SQL state.
> It would be nice to have the same information in the output as what is
> written by the embedded driver (or client driver running with jdk
> 1.5).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message