| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Stefan Reiser <s(dot)reiser(at)tu-braunschweig(dot)de> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, zelaine(at)amazon(dot)com, pgsql-bugs(at)postgresql(dot)org, List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |
| Date: | 2013-01-11 17:21:37 |
| Message-ID: | alpine.BSO.2.00.1301111220300.28737@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2013-01-11 17:23:18 | Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |
| Previous Message | Dave Cramer | 2013-01-11 16:59:10 | Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2013-01-11 17:23:18 | Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |
| Previous Message | Dave Cramer | 2013-01-11 16:59:10 | Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |