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

Поиск
Список
Период
Сортировка
От Dave Cramer
Тема Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)?
Дата
Msg-id A3D1BE07-7266-4DCF-859A-69C67E44B3EF@fastcrypt.com
обсуждение исходный текст
Ответ на Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)?  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)?  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-jdbc
On 1-Mar-07, at 7:06 PM, Tom Lane wrote:

> 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.

This means you have to leave all parameter types as UNKNOWN. What's
the point of having parameter types at all ?

Dave
>             regards, tom lane
>


В списке pgsql-jdbc по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)?