Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception
Date
Msg-id alpine.BSO.2.00.1301111220300.28737@leary.csoft.net
Whole thread Raw
In response to Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception  (Stefan Reiser <s.reiser@tu-braunschweig.de>)
List pgsql-jdbc

On Fri, 11 Jan 2013, Stefan Reiser wrote:

> What about returning Statement.SUCCESS_NO_INFO as it says in
> http://docs.oracle.com/javase/6/docs/api/java/sql/BatchUpdateException.html#getUpdateCounts%28%29
> and
> http://docs.oracle.com/javase/6/docs/api/java/sql/Statement.html#executeBatch%28%29
>
> It seems better to report no number at all rather than a number (INT_MAX) that
> is known to be wrong.

What about Statement.executeUpdate?  It has provision for returing a
batch execution response code.

Kris Jurka


pgsql-jdbc by date:

Previous
From: Dave Cramer
Date:
Subject: Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception
Next
From: Kris Jurka
Date:
Subject: Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception