| From: | Barry Lind <barry(at)xythos(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL jdbc list <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Using boolean '1' in jdbc2 |
| Date: | 2001-09-14 01:50:02 |
| Message-ID: | 3BA1624A.8020506@xythos.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Peter,
Good question. There was a mail thread on this probably about six
months ago. IIRC this was done so that you could call getBoolean() on
an integer column. I think that some other database supported this and
they wanted to have postgres support it in the same way. I think that
is when the jdbc1 code was patched to support the value '1'. I don't
know why the jdbc2 code wasn't changed at the same time.
thanks,
--Barry
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
>
>>I noticed that jdbc1 getBoolean allows '1', while jdbc2 does not. The
>>following patch makes jdbc2 accept '1' also. Is this OK?
>>
>
> Why? Booleans always come out as 't' or 'f'.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Glenn R. Kronschnabl | 2001-09-14 03:58:23 | Re: Using boolean '1' in jdbc2 |
| Previous Message | Rene Pijlman | 2001-09-13 19:46:41 | Re: Using boolean '1' in jdbc2 |