Re: Postgres 8.0 + JDBC
От
Kris Jurka
Тема
Re: Postgres 8.0 + JDBC
Дата
Msg-id
Pine.BSO.4.56.0410051527310.11868@leary.csoft.net
Ответ на
Re: Postgres 8.0 + JDBC (Oliver Jowett)
Список
Дерево обсуждения
Postgres 8.0 + JDBC "Johann Robette" <jrobette@onyme.com>
Re: Postgres 8.0 + JDBC Oliver Jowett <oliver@opencloud.com>
RE : Postgres 8.0 + JDBC "Johann Robette" <jrobette@onyme.com>
Re: RE : Postgres 8.0 + JDBC Kris Jurka <books@ejurka.com>
Re: RE : Postgres 8.0 + JDBC Kris Jurka <books@ejurka.com>
Re: Postgres 8.0 + JDBC Oliver Jowett <oliver@opencloud.com>
Fix setArray() when using the v3 protocol (was Re: Postgres
8.0 + JDBC) Oliver Jowett <oliver@opencloud.com>
Re: Fix setArray() when using the v3 protocol (was Re: Postgres 8.0 + JDBC) Tom Lane <tgl@sss.pgh.pa.us>
Re: Fix setArray() when using the v3 protocol (was Re: Postgres Oliver Jowett <oliver@opencloud.com>
Re: Fix setArray() when using the v3 protocol (was Re: Postgres Kris Jurka <books@ejurka.com>
Re: Postgres 8.0 + JDBC Kris Jurka <books@ejurka.com>
Re: Postgres 8.0 + JDBC Oliver Jowett <oliver@opencloud.com>
Re: Postgres 8.0 + JDBC Tom Lane <tgl@sss.pgh.pa.us>
On Wed, 6 Oct 2004, Oliver Jowett wrote:
> It seems possible to fix the driver to handle this case by making
> setArray() derive a proper array type name i.e. ("_" +
> Array.getBaseType()), and using that rather than 'text' as the parameter
> type.
>
Wouldn't it be simpler to change setArray to call setString with 0 as the
type oid allowing the backend to figure out what to do with it? Perhaps
it would have trouble determining the type if the underlying function was
overloaded, but other than that I don't see a problem.
Kris Jurka
В списке pgsql-jdbc по дате отправления
