Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)? - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)?
Date
Msg-id 23779.1172793964@sss.pgh.pa.us
Whole thread Raw
In response to Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)?  (Dave Cramer <pg@fastcrypt.com>)
Responses Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)?  (Dave Cramer <pg@fastcrypt.com>)
List pgsql-jdbc
Dave Cramer <pg@fastcrypt.com> writes:
> The reason that setNull is required is because the type information
> is required. NULL by it self has no type information. The jdbc driver
> binds values to a prepared statement and the type information is
> required. So setNull( n, typeinfo) is required to bind the correct type.

At least in this particular case, leaving the parameter type as UNKNOWN
would have worked as the OP wishes.  I dunno if that would break other
cases though.

            regards, tom lane

pgsql-jdbc by date:

Previous
From: Dave Cramer
Date:
Subject: Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)?
Next
From: Dave Cramer
Date:
Subject: Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)?