Re: CachedRowSetXImpl() and PostgreSQL - Mailing list pgsql-jdbc

From Poul Møller Hansen
Subject Re: CachedRowSetXImpl() and PostgreSQL
Date
Msg-id 45130543.7080609@pbnet.dk
Whole thread Raw
In response to Re: CachedRowSetXImpl() and PostgreSQL  (Oliver Jowett <oliver@opencloud.com>)
Responses Re: CachedRowSetXImpl() and PostgreSQL
List pgsql-jdbc
> What we need to know is what is the metadata call being made to the
> driver and how do the results differ from what is expected?
>
That's pretty much hidden behind the curtains in the Java classes. How
can I log that ?

> BTW, it's possible to have a table called "my.table" (where "my." is
> part of the table name, not a schema prefix) so the driver seems to be
> doing the right thing if it is being asked about tables called
> "my.table" by the RowSet .. But that's why we need to know what
> metadata call is being made.
>
my is the schema name. I have tried 3 setups:
1. setting setTableName("my.table");
2. setTableName("table");
3. setSchemaName("my");  setTableName("table");

And none of them works. When getting the metadata from pg_catalog the
schema name must be left out
and when doing update the schema name must be included or it can't find
the relation.
It's like the setSchemaName has no effect
> I think finding out why setSchemaName on your rowset does not work is
> the first step, that RuntimeException tells me nothing about the real
> cause of the problem.
Exactly, but I'm clueless how.


Poul


pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: CachedRowSetXImpl() and PostgreSQL
Next
From: Oliver Jowett
Date:
Subject: Re: CachedRowSetXImpl() and PostgreSQL