db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anurag Shekhar <Anurag.Shek...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-819) Provide JDBC4 SQLException subclasses support in Embedded driver
Date Tue, 14 Feb 2006 19:31:36 GMT

> What's the benefit of having the embedded driver not call the
> Util.notImplemented() method and thus increasing the footprint for no value?
>
> Wouldn't fixing the client's use first make sense? Then the
> Util.notImplemented() method could remain.
>
> Dan.
>
>   
I have added a new issue and attached a path to remove the reference of 
engine class in network client.
In jdbc40 the exception thrown depends on the SQLState but in prior 
versions its only SQLException.
So it needs two difference classes to construct exception (for jdbc4.0 
and prior).
Probably NOT_IMPLEMENTED is an exception case where the at the time of 
construction
itself we know that it doesn't needs any jdbc4.0 classes. But won't it 
be appropriate to keep
all the methods creating exception in one place ?

anurag





Mime
View raw message