Re: Found a Bug in latest Driver (I THINK) and pg 8.4

Right in my case my schema changes as each organization has a separate
schema.

I would love to be able to set the schema with the typeName. Why couldn't
that be a seperate attribute in Java setLookupSchema and if not set function
as it does now. Wouldn't this handle both cases.

While I know I am using an outside case I do think it is a valid one.

On Tue, Jun 1, 2010 at 4:34 PM, Kris Jurka <books(at)ejurka(dot)com> wrote:

>
>
> On Tue, 1 Jun 2010, Jason Tesser wrote:
>
> The issue with teh driver is that when you use a composite type as an
>> INPUT
>> parameter of a STored Proc teh Driver queries the pg_catalog but from what
>> I
>> can tell has no way of telling what schema to query for.
>>
>
> Right, the JDBC driver's internal knowledge of types has no information
> about schemas or the search path. It currently assumes the name alone is a
> unique identifier. Fixing this to respect the search path wouldn't be that
> tough by using the regtype type, but we want to cache this information to
> avoid repeated type lookups, so it wouldn't change as the search_path
> changed. The other approach to fixing things would be to allow the user to
> specify the schema with the type name, but I don't think people want to do
> that because the schema may not be known to the application.
>
> Kris Jurka
>