Re: Utilizing executeBatch() with stored procedures - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: Utilizing executeBatch() with stored procedures
Date
Msg-id 1704D65B-2866-4FAB-8EE6-E8017A01EE7D@fastcrypt.com
Whole thread Raw
In response to Re: Utilizing executeBatch() with stored procedures  ("Guy Rouillier" <guyr@masergy.com>)
Responses Re: Utilizing executeBatch() with stored procedures
List pgsql-jdbc
Guy, Kris,

What was the suggested fix ?

Dave
On 30-Jun-06, at 12:37 PM, Guy Rouillier wrote:

> Yukino Miyazawa wrote:
>> I was wondering what the status is for getting CallableStatments to
>> run via executeBatch() to get inserts done in bulk. I've been
>> attempting to get this to work on 8.1.4 with the  8.2 503 driver.
>> Despite my return type being void, this fails to execute returning a
>> syntax error on "{" which is alluding to the "{call func(? . . ."
>>
>> Are there any known workarounds?
>
> I've tried this myself and didn't get a syntax error.  However,
> invoking
> stored functions in executeBatch currently does not work.  Even though
> you use "call func" in your SQL command, the PostgreSQL JDBC driver
> maps
> this to "select func" because that is what PG requires.  Now, even
> though your stored function returns void, the result of a select is
> always a ResultSet, empty in this case.  But that is enough to cause
> executeBatch to generate an error complaining that no return value is
> allowed.
>
> I discussed with Kris Jurka a way to address this issue, but I haven't
> had time to try his solution yet.
>
> --
> Guy Rouillier
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: explain analyze is your friend
>


pgsql-jdbc by date:

Previous
From: Tom Lane
Date:
Subject: Re: JDBC driver bug?
Next
From: Danny Schueler
Date:
Subject: jdbc integer value oid to big!