Poul Møller Hansen wrote:
>
>> 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 ?
Well, we have exactly the same problem, without seeing the code that
calls the driver it is very difficult to know if the fault lies with the
driver or the calling code.
I think there are some intercepting JDBC driver wrappers that might help
you with the "what is the metadata call" bit (I can't remember the name
of one offhand) but the "how do the results differ" requires some
knowledge of what the calling code is expecting.. which probably means
"contact the implementor of your RowSet".
>> 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")
I would expect (3) to be what you need.
>> 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.
Again I think this is going to be "talk to the RowSet implementor"
unfortunately.
-O
