Usage of standard SQL subclasses for exceptions are in H2 roadmap for a 
long time.

But this may be quite complicated because H2 actually use own subclass for 
exceptions with additional functionality, so either this functionality 
should be implemented in some other way or all exceptions should have H2's 
own subclasses that seems to be an overkill. We need to take a some 
decision about this.

>From my point of view it's better to drop JdbcSQLException and reimplement 
it's functionality somehow and use only standard classes from Java. 
Exceptions may be passed through RMI, for example, to client that doesn't 
have an H2 library it its classpath.

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 https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

Reply via email to