| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Guy Rouillier <guyr(at)masergy(dot)com> |
| Cc: | PostgreSQL JDBC <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: JDBC support for CALL / PERFORM |
| Date: | 2006-02-14 00:29:45 |
| Message-ID: | Pine.BSO.4.63.0602131914140.13706@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Mon, 13 Feb 2006, Guy Rouillier wrote:
>
> Ok, thanks. I haven't begun to look at the code yet, but the general
> approach will be
>
> (1) Execute each statement in the batch one at a time.
> (2) If a particular statement encounters this one error (result not
> allowed in batch), and if the statement is a callable statement, then
> absorb the error, discard the result set and continue.
> (3) Otherwise (not this particular error or not a callable statement),
> then allow the error to propagate as currently implemented.
>
All you should have to modify is
org.postgresql.jdbc2.AbstractJdbc2Statement.BatchResultHandler.handleResultRows
to not throw an Exception if you've got a CallableStatement.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Radek Jíra | 2006-02-14 14:26:23 | An I/O error occured while sending to the backend |
| Previous Message | Guy Rouillier | 2006-02-14 00:07:09 | JDBC support for CALL / PERFORM |