Merge pull request #203 from Montana/patch-2

`Statement` and `ResultSet` were never closed.closed statements. If more tests or queries run in the same JVM, these unclosed resources can pile up and cause connection pool exhaustion or memory leaks.

Author: mikebell90

src/test/java/com/opentable/db/postgres/embedded/LiquibasePreparerContextTest.java

@@ -26,16 +26,20 @@
 import static org.junit.Assert.assertEquals;
 
 public class LiquibasePreparerContextTest {
-    @Rule
-    public PreparedDbRule db = EmbeddedPostgresRules.preparedDatabase(LiquibasePreparer.forClasspathLocation("liqui/master-test.xml", new Contexts("test")));
+  @Rule
+  public PreparedDbRule db = EmbeddedPostgresRules.preparedDatabase(
+      LiquibasePreparer.forClasspathLocation("liqui/master-test.xml", new Contexts("test"))
+  );
 
-    @Test
-    public void testEmptyTables() throws Exception {
-        try (Connection c = db.getTestDatabase().getConnection();
-             Statement s = c.createStatement()) {
-            ResultSet rs = s.executeQuery("SELECT COUNT(*) FROM foo");
-            rs.next();
-            assertEquals(0, rs.getInt(1));
-        }
+  @Test
+  public void testEmptyTables() throws Exception {
+    try (Connection c = db.getTestDatabase().getConnection();
+         Statement s = c.createStatement();
+         ResultSet rs = s.executeQuery("SELECT COUNT(*) AS cnt FROM foo")) {
+
+      rs.next();
+      long count = rs.getLong("cnt");
+      assertEquals(0L, count);
     }
+  }
 }