Re: executeBatch() issue with new driver? - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: executeBatch() issue with new driver?
Date
Msg-id Pine.BSO.4.56.0411021427540.3642@leary.csoft.net
Whole thread Raw
In response to executeBatch() issue with new driver?  (Alan Stange <stange@rentec.com>)
Responses Re: executeBatch() issue with new driver?
List pgsql-jdbc

On Tue, 2 Nov 2004, Alan Stange wrote:

> >This is something (as discussed with Dave) that you shouldn't be doing,
> >
> Let me be devils advocate for a second and ask "why not"?   I don't
> disagree,  but I'm not sure I understand all the issues here.
>

The real problem is that executeBatch() returns an int[] of update counts.
What should we return for an entry like addBatch("INSERT ... ; INSERT
..."); ?  Two individual entries? The sum of the update counts?  The
javadoc for executeBatch isn't entirely clear, but certainly seems to make
the assumption that one batch entry is one command.  Especially since you
are already using addBatch, there doesn't seem to be much point in jamming
two commands into one batch.

Kris Jurka

pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: executeBatch() issue with new driver?
Next
From: Vadim Nasardinov
Date:
Subject: 1300 to 3100 lines of code for XA support (was: Re: plans and estimates for supporting JDBC 3.0)