Robert Manning wrote:
> On 10/19/06, Lars Heill <Lars.Heill@...> wrote:
>> Robert Manning wrote, On 10/19/06 03:43:
>>> On 10/18/06, Lars Heill <Lars.Heill@...> wrote:
>>>> Lars Heill wrote:
>>>>> Only I do not see any of my tables or views in the various
>>>>> schemas, just a generic
>>>>> SYSTEM TABLE
>>>>> Refreshing "Tree and Cache" or "Item", I see my table names
>>>>> flash by on the status line, but no tables/views show up in
>>>>> the object tree.
>>> DatabaseMetaData is used to build the object tree. supportsSchemas or
>>> supportsCatalogs need to return true. Beyond that getTables needs to return
>>> the tables for the selected schema/catalog.
>>>> In case it matters: it is a JDBC 3.0 driver, and the database
>>>> has 72 schemas.
>>> I believe I've seen this issue with SQLBase in the past due to an incomplete
>>> driver implementation. What database and driver are you using? Any exceptions
>>> in the log?
>> Thanks Rob,
>> I have done some more checking, and it turns out it is not a problem
>> with my database or driver (Sun HADB), as everything works nicely in
>> StarOffice 8 and in SQuirreL 2.2 final.
>> Below are snippets from my attempts with SQuirreL 2.3 final (which I
>> tried on both Windows XP pro and Solaris 10 x86), showing some exceptions
>> I get whenever I try to browse a TABLE or VIEW object:
>> * GUI work done in wrong thread
>> * GUI Thread is doing database work
>> Is this a known issue? - with a known workaround?
> No, the messages about work being done in the wrong thread are performance
> reminders for the developers. Generally it's not good to use the GUI
> thread for
> database work, or the application threads for GUI work. Not saying it doesn't
> happen - it does - but generally it's not good. I've removed those message for
> 2.4 because they obscure any other debug messages.
> When you refresh the object tree in 2.3, does that change anything. Are you
> using the new schema caching which just became available in 2.3?
Refreshing the object tree or an item in it does not change anything.
Messages whizz past on the status line, and I believe I recognize my
table names there (a lot, difficult to tell).
I have tried all kinds of caching, yes; on everything, and on select
schemas: no effect on the object tree.
If you believe any later public builds might affect this, I would be
willing to test them.