Hi, 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. Regards, Thomas On Fri, Aug 23, 2013 at 4:50 PM, Nicolas Fortin (OrbisGIS) < [email protected]> wrote: > Your unit test is better. > > However org.h2.api should contain java interface. This will give you more > freedom in future implementations without break anything. > > > -Nicolas Fortin > Atelier SIG > IRSTV FR CNRS 2488 > > Le vendredi 23 août 2013 15:48:33 UTC+2, Noel Grandin a écrit : > >> >> On 2013-08-23 15:02, Nicolas Fortin (OrbisGIS) wrote: >> > Here the h2 branch where exception info is added: >> > >> > https://github.com/nicolas-f/**h2database/tree/feature/**exception-info<https://github.com/nicolas-f/h2database/tree/feature/exception-info> >> >> Thank you very much, your patch has been committed (with some changes). >> > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
