| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | Andres Ledesma <aledes(at)euskalnet(dot)net>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: postgresql and java data types mismatch..... |
| Date: | 2005-08-19 05:03:31 |
| Message-ID: | Pine.BSO.4.62.0508190001320.11917@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Fri, 12 Aug 2005, Oliver Jowett wrote:
> Andres Ledesma wrote:
>
>> A CallableStatement Function was executed and the return was of type
>> (java.sql.Types=-7) however type=java.sql.Types=16 was registered.
>>
>> Types = -7 correspond to Types.BIT
>> Types = 16 correspond to Types.BOOLEAN
>
> A workaround is to just register the OUT parameter as Types.BIT, but
> yes, the driver shouldn't really complain in this case.
>
Just to follow up on this, the 8.0 and 8.1 drivers correctly handle this
and do not report an error. It is still possible to generate this error
with the new drivers by using the JDBC 2 version of the driver because it
doesn't understand the JDBC 3 type BOOLEAN and thereforce cannot map it
correctly.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2005-08-19 05:34:38 | Re: Updated high-unicode patch |
| Previous Message | Kris Jurka | 2005-08-19 04:33:06 | Re: Memory leak in 8.0 JDBC driver? |