Skip site navigation (1) Skip section navigation (2)

JDBC Statement.executeBatch patch

From: Rene Pijlman <rpijlman(at)wanadoo(dot)nl>
To: pgsql-patches(at)postgresql(dot)org
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: JDBC Statement.executeBatch patch
Date: 2001-08-26 18:41:37
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbcpgsql-patches
Attached is a patch for current CVS, consisting of a cvs diff -c
for the changed files and a few new files:
- test/jdbc2/
- util/
- jdbc2/

As an aside, is this the best way to submit a patch consisting
of both changed and new files? Or is there a smarter cvs command
which gets them all in one patch file?

This patch fixes batch processing in the JDBC driver to be
JDBC-2 compliant. Specifically, the changes introduced by this
patch are:

1) Statement.executeBatch() no longer commits or rolls back a
transaction, as this is not prescribed by the JDBC spec. Its up
to the application to disable autocommit and to commit or
rollback the transaction. Where JDBC talks about "executing the
statements as a unit", it means executing the statements in one
round trip to the backend for better performance, it does not
mean executing the statements in a transaction.

2) Statement.executeBatch() now throws a BatchUpdateException()
as required by the JDBC spec. The significance of this is that
the receiver of the exception gets the updateCounts of the
commands that succeeded before the error occurred. In order for
the messages to be translatable, java.sql.BatchUpdateException
is extended by org.postgresql.jdbc2.PBatchUpdateException() and
the localization code is factored out from
org.postgresql.util.PSQLException to a separate singleton class

3) When there is no batch or there are 0 statements in the batch
when Statement.executeBatch() is called, do not throw an
SQLException, but silently do nothing and return an update count
array of length 0. The JDBC spec says "Throws an SQLException if
the driver does not support batch statements", which is clearly
not the case. See testExecuteEmptyBatch() in for an example. The message
postgresql.stat.batch.empty is removed from the language
specific properties files.

4) When Statement.executeBatch() is performed, reset the
statement's list of batch commands to empty. The JDBC spec isn't
100% clear about this. This behaviour is only documented in the
Java tutorial
Note that the Oracle JDBC driver also resets the statement's
list in executeBatch(), and this seems the most reasonable
5) A new test case is added to the JDBC test suite which tests
various aspects of batch processing. See the new file

René Pijlman

Attachment: patch.diff
Description: text/plain (9.9 KB)
Description: text/plain (4.9 KB)
Description: text/plain (1.5 KB)
Description: text/plain (859 bytes)


pgsql-patches by date

Next:From: Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=Date: 2001-08-26 18:46:54
Subject: Re: Re: [PATCHES] Makefile.PL for
Previous:From: Larry RosenmanDate: 2001-08-26 17:48:11
Subject: Re: Re: [PATCHES] Makefile.PL for

pgsql-jdbc by date

Next:From: Anders BengtssonDate: 2001-08-26 18:57:42
Subject: Attempt to clean up ExecSql() in JDBC
Previous:From: Bruce MomjianDate: 2001-08-26 17:09:29
Subject: Re: [JDBC] Re: Bug #428: Another security issue with the JDBC driver.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group