Lance J. Andersen wrote: > There are still a fair amount of applications which utilize these > methods. I am not removing these methods in JDBC 4 and infact I > actually clarified the api docs for them. > > Derby should implement these IMHO.
We are making a new JDBC driver and these are deprecated methods. We throw not implemented exceptions for embedded and right now in the client, they are there but are broken (can cause protocol errors and loss of connection). I guess if you wanted to spend a lot of time to implement them for both embedded and client, I wouldn't object strongly to having them, but in general my vote would be to throw a not implemented exception like we do for embedded at least for now. Thanks Kathey
