Re: tightening up on use of oid 0
От | Oliver Jowett |
---|---|
Тема | Re: tightening up on use of oid 0 |
Дата | |
Msg-id | 4166F72E.9010201@opencloud.com обсуждение исходный текст |
Ответ на | Re: tightening up on use of oid 0 (Kris Jurka <books@ejurka.com>) |
Ответы |
Re: tightening up on use of oid 0
|
Список | pgsql-jdbc |
Kris Jurka wrote: > > 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. OK, so getValue() and toString() return null? This would still mean that setNull() would not work for Types.OTHER, though. -O
В списке pgsql-jdbc по дате отправления: