Re: Fix setArray() when using the v3 protocol (was Re: Postgres 8.0 + JDBC)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Fix setArray() when using the v3 protocol (was Re: Postgres 8.0 + JDBC)
Date: 2004-10-08 03:04:41
Message-ID: 27750.1097204681@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-jdbc

Oliver Jowett <oliver(at)opencloud(dot)com> writes:
> ! // Use a typename that is "_" plus the base type; this matches how the
> ! // backend looks for array types.
> ! String typename = "_" + x.getBaseTypeName();
> ! int oid = connection.getPGType(typename);
> ! if (oid == Oid.INVALID)
> ! throw new PSQLException("postgresql.prep.typenotfound", PSQLState.INVALID_PARAMETER_TYPE, typename);

Er, what about schema-qualified type names? Also, are you sure that
getBaseTypeName will return the correct internal type name, eg "int8"
not "bigint"?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Oliver Jowett 2004-10-08 03:30:30 Re: Fix setArray() when using the v3 protocol (was Re: Postgres
Previous Message Tom Lane 2004-10-08 02:55:03 Re: Question from a newbie

Browse pgsql-jdbc by date

  From Date Subject
Next Message Oliver Jowett 2004-10-08 03:30:30 Re: Fix setArray() when using the v3 protocol (was Re: Postgres
Previous Message Oliver Jowett 2004-10-08 02:13:06 Fix setArray() when using the v3 protocol (was Re: Postgres 8.0 + JDBC)