On Sat, Aug 24, 2013 at 11:19 AM, Thomas Mueller
<thomas.tom.muel...@gmail.com> wrote:
> I'm not convinced that using another exception class is a good idea. This
> new exception class has to be supported in multiple places (remoting the
> exception for example).
>
> What about extending the existing class (JdbcSQLException) with the required
> data? If it's not a parse exception, then the field is empty.
That's a pity.
Using an exception subclass makes the exception handling very natural.
It's exactly how catch blocks are meant to be used.
try {
...
} catch (JdbcParseSQLException ex) {
...show syntax error...
} catch (SQLException ex) {
.. show more serious error...
}
But if we go your way, we need to move JdbcSQLException into the
org.h2.api package.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
