| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Ludovico Bianchini <metlud(at)yahoo(dot)it> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: ResultSet with more than 5 rows causes error |
| Date: | 2007-10-15 08:07:48 |
| Message-ID: | Pine.BSO.4.64.0710150406560.15470@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Mon, 1 Oct 2007, Kris Jurka wrote:
> I've managed to reproduce this problem with the attached test case.
> At fault are the ill conceived side effects in
> org.postgresql.core.v3.SimpleParameterList#getTypeOID. An accessor
> like getTypeOID shouldn't be responsible for setting a value for the
> out parameter. getTypeOID is called from QueryExecutorImpl's
> sendParse method, which obviously isn't called when we reuse a server
> side prepared statement and don't need to reparse. This leaves an
> uninitialized value in the paramValues array which we die on later.
>
I've applied a fix for this in CVS to 8.1, 8.2 and 8.3dev and it will be
included in the next release.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tore Halset | 2007-10-16 06:05:58 | text metadata |
| Previous Message | Heikki Linnakangas | 2007-10-11 18:52:01 | Re: Support for distributed transactions |