]> granicus.if.org Git - postgresql/commit
Fixed bug reported by Marko Strukelj and Keith Wannamaker. Using executeBatch
authorBarry Lind <barry@xythos.com>
Wed, 20 Nov 2002 07:34:32 +0000 (07:34 +0000)
committerBarry Lind <barry@xythos.com>
Wed, 20 Nov 2002 07:34:32 +0000 (07:34 +0000)
commit54bc3b6b8be32e246a40af44583b22072cee8cde
tree0de16a17667fe2b3d41dba2dea0ff74d964c5d51
parentb60be3f2f8d094da79e04c6eda888f401b09dc39
Fixed bug reported by Marko Strukelj and Keith Wannamaker.  Using executeBatch
on a preparedStatement would reset the prepared statment causing subsequent
uses of the preparedStatement to fail (i.e. the following series of calls
would fail: addBatch() executeBatch() addBatch() executBatch()).  This is
a regression from 7.2 where this worked correctly.  The regression test has
also been modified to explicitly test for this case.

 Modified Files:
  jdbc/org/postgresql/jdbc1/AbstractJdbc1Statement.java
  jdbc/org/postgresql/jdbc2/AbstractJdbc2Statement.java
  jdbc/org/postgresql/test/jdbc2/BatchExecuteTest.java
src/interfaces/jdbc/org/postgresql/jdbc1/AbstractJdbc1Statement.java
src/interfaces/jdbc/org/postgresql/jdbc2/AbstractJdbc2Statement.java
src/interfaces/jdbc/org/postgresql/test/jdbc2/BatchExecuteTest.java