Comments on: go jdbc! http://malvasiabianca.org/archives/2006/02/go-jdbc/ Fri, 10 Feb 2012 05:54:57 +0000 hourly 1 http://wordpress.org/?v=3.3 By: david carlton http://malvasiabianca.org/archives/2006/02/go-jdbc/comment-page-1/#comment-4425 david carlton Fri, 03 Mar 2006 17:26:59 +0000 http://malvasiabianca.org/?p=313#comment-4425 Throwing exceptions is good - the database connection could go south at any time, after all, and I'd rather have exceptions than return codes. And I would even be forced to concede that, if we're going to make a checked exception / unchecked exception distinction, that the exceptions should be checked. I just don't believe in the whole checked exception thing in the first place. (Though it is admittedly less of a misfeature in Java than in C++.) I'm of two minds as to what I should do in my own code here - when I translate these exceptions into my own exception type, should I make my own exceptions be checked or unchecked? In the past, I've gone with the former, because in general I like to write code that's idiomatic in the language that I'm using. But if I were to do that in this case, I would have to stick a throw spec on tons and tons of methods; this would in no way improve clarity, and given that I'm only planning to catch exceptions at the top level, it wouldn't improve safety either. Throwing exceptions is good – the database connection could go south at any time, after all, and I’d rather have exceptions than return codes. And I would even be forced to concede that, if we’re going to make a checked exception / unchecked exception distinction, that the exceptions should be checked. I just don’t believe in the whole checked exception thing in the first place. (Though it is admittedly less of a misfeature in Java than in C++.)

I’m of two minds as to what I should do in my own code here – when I translate these exceptions into my own exception type, should I make my own exceptions be checked or unchecked? In the past, I’ve gone with the former, because in general I like to write code that’s idiomatic in the language that I’m using. But if I were to do that in this case, I would have to stick a throw spec on tons and tons of methods; this would in no way improve clarity, and given that I’m only planning to catch exceptions at the top level, it wouldn’t improve safety either.

]]> By: Roger Standridge http://malvasiabianca.org/archives/2006/02/go-jdbc/comment-page-1/#comment-4424 Roger Standridge Fri, 03 Mar 2006 17:21:32 +0000 http://malvasiabianca.org/?p=313#comment-4424 Grrr... API's that throw exceptions. There ought to be an automated way to deal with this kind of mis-feature. Grrr… API’s that throw exceptions. There ought to be an automated way to deal with this kind of mis-feature.

]]>