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

From Alan Stange
Subject Re: executeBatch() issue with new driver?
Date
Msg-id 4187EBA4.2040100@rentec.com
Whole thread Raw
In response to Re: executeBatch() issue with new driver?  (Kris Jurka <books@ejurka.com>)
Responses Re: executeBatch() issue with new driver?
Re: executeBatch() issue with new driver?
List pgsql-jdbc
Kris Jurka wrote:

>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.
>
This was what I was thinking.   What does the pg74 driver do in this
case as it does allow multiple statements in each batch?

> Especially since you
>are already using addBatch, there doesn't seem to be much point in jamming
>two commands into one batch.
>
>
Network latency.   We were able to greatly increase performance this way
by reducing the number of round trips.

-- Alan




pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: 1300 to 3100 lines of code for XA support
Next
From: Vadim Nasardinov
Date:
Subject: Re: 1300 to 3100 lines of code for XA support