> + catch (SQLException e){
> + System.out.format("SQLException: %s%n", e.getMessage());
> + System.out.format("SQLState: %s%n", e.getSQLState());
> + System.out.format("VendorError: %s%n", e.getErrorCode());
> + e.printStackTrace();
> +
> + return false;
> + }
> + finally {
> + // Release resources in reverse order of creation.
> +
> + if (rs != null) {
> + try {
> + rs.close();
> + }
> + catch (SQLException sqlEx) {
Apparently this is the prescribed way @zack-shoylev found to close JDBC
resources.
http://dev.mysql.com/doc/refman/5.6/en/connector-j-usagenotes-last-insert-id.html
I don't think the Exception needs to be renamed considering the comment below
it.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/21/files#r6927253
