Re: tightening up on use of oid 0

On Fri, 8 Oct 2004, Oliver Jowett wrote:
> 
> Executing "SELECT foo(?)" via PreparedStatement will work fine if you 
> pass a non-null PGline or PGbox argument to setObject, but if you try to 
> setNull() then you will get ambiguity between the two functions at 
> execution time.
> 
> I can't see a way to fix this without a postgresql extension of some 
> sort. Options I can think of are:

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.

Kris Jurka