database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-09-11 00:12:06 +03:00
Code Activity

Fixed bug reported by Marko Strukelj and Keith Wannamaker. Using executeBatch

Browse Source 
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
This commit is contained in:
Barry Lind
2002-11-20 07:34:32 +00:00
parent b60be3f2f8
commit 54bc3b6b8b
3 changed files with 49 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
src/interfaces/jdbc/org/postgresql/test/jdbc2/BatchExecuteTest.java
View File

@@ -157,11 +157,19 @@ public class BatchExecuteTest extends TestCase
pstmt.executeBatch();
assertCol1HasValue(7);
con.commit();
//now test to see that we can still use the statement after the execute
pstmt.setInt(1, 3);
pstmt.addBatch();
assertCol1HasValue(7);
pstmt.executeBatch();
assertCol1HasValue(10);
con.commit();
assertCol1HasValue(10);
con.rollback();
assertCol1HasValue(7);
assertCol1HasValue(10);
pstmt.close();
}