Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)?

Ok, looking at the code in the driver we should be doing the right
thing.

setObject(n,null) will set the Oid to UNSPECIFIED

Any chance we can get a test case to see how this fails ?

Dave
On 1-Mar-07, at 8:15 PM, Dave Cramer wrote:

>
> On 1-Mar-07, at 7:16 PM, Tom Lane wrote:
>
>> Dave Cramer <pg(at)fastcrypt(dot)com> writes:
>>> On 1-Mar-07, at 7:06 PM, Tom Lane wrote:
>>>> 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.
>>
>>> This means you have to leave all parameter types as UNKNOWN. What's
>>> the point of having parameter types at all ?
>>
>> No, only the ones you do not have any knowledge about. The OP's
>> complaint is basically that the driver is forcing the parameter type
>> to "varchar" on the basis of nothing whatsoever.
>>
> OK, this makes some sense, If they do setObject(n, null) then we
> bind the type to UNKNOWN. If they do setInt(n, null) we can
> actually get that one right.
>
> Dave
>> regards, tom lane
>>
>> ---------------------------(end of
>> broadcast)---------------------------
>> TIP 2: Don't 'kill -9' the postmaster
>>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>