db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anurag Shekhar (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-819) Provide JDBC4 SQLException subclasses support in Embedded driver
Date Tue, 21 Feb 2006 18:09:21 GMT
     [ http://issues.apache.org/jira/browse/DERBY-819?page=all ]

Anurag Shekhar updated DERBY-819:

    Attachment: derby-819_3.diff

Main changed I have made in this patch since the last submission
	I have moved back the exception methods of Utils.
	Now the exceptionFactory is a static member of Utils which is initialized during declaration
itself so when this will never be null hence eliminating the possibility of NPE
	This variable is overwritten by SQLException40 instance by Driver40 during boot.
	Merged the two method of SQLExceptionFactory40.
	In newly created exception pointed the stack trace to root cause (if there is another exception

Other issues
	Fixed the copyright dates.
	Modified test code to check SQLSTATE
	Added comments in SQLException40 class and getSQLException method of the same.
Open Issues	
	derbyall has many failure (even without this patch) when executed with jdk1.6. I will be
creating a  jira issue for this.
	After these changes all the tests which are comparing the exception thrown or printing the
exception will fail.

> Provide JDBC4 SQLException subclasses support in Embedded driver
> ----------------------------------------------------------------
>          Key: DERBY-819
>          URL: http://issues.apache.org/jira/browse/DERBY-819
>      Project: Derby
>         Type: Sub-task
>   Components: JDBC
>  Environment: all
>     Reporter: Anurag Shekhar
>     Assignee: Anurag Shekhar
>     Priority: Minor
>  Attachments: .derby-819_2.stat, derby-819-onlyforreview.diff, derby-819.diff, derby-819_2.diff,
derby-819_3.diff, stat.out

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message