From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: tightening up on use of oid 0 |
Date: | 2004-10-08 23:07:17 |
Message-ID: | Pine.BSO.4.56.0410081803430.6860@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Sat, 9 Oct 2004, Oliver Jowett wrote:
> > Can't the existing PGobject interface handle this. You can create a
> > PGobject with the correct datatype and a null value and that should work.
>
> OK, so getValue() and toString() return null?
Right.
> This would still mean that setNull() would not work for Types.OTHER, though.
>
I don't think this is a very big deal. The only place this looks
important is for an overloaded function call. The previous driver didn't
have any typing at all for NULLs, and I can only recall one complaint
about. The other API additions you suggested didn't really appeal to me
and we have an "out" with PGobject, so I think we're OK here.
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2004-10-09 00:09:34 | Re: Using gettext |
Previous Message | Kris Jurka | 2004-10-08 23:03:23 | New jdbc website |