#1173 Squirrel SQL FX connect to DB2, but doesn't show table structure, nor data

[Nick]

Hi,

I'm trying the new Squirrel SQL FX, but I have an issue with the DB2 database.
I use the DB2 JCC4 Driver that works very well with the usual Squirrel SQL Client.
The connection is ok; I can see the schema trees with my tables and synonyms.
The problem is that when I click on a table, there is an error and I don't see any details of the table.
Same problem when I try to execute a simple select query. There is an error and no results.

Attached to this ticket there is the error log.

[Gerd Wagner]

Could you please give squirrelsqlfx-snapshot-20150428_0018 a try.

I don't have access to DB2 right now but I hope the change I made will fix the problem.

Please let me know if it worked.

[Nick]

Hi,

there is a good new and a bad one :-)

The good new is that now the queries in the SQL tab are working well.
The bad new is that in the Objects tab I still have the problem. I can see only the list of the objects, but no details. If I click on an object there is an error. I have attached the log with the messages.

Regards
Nicola

[Gerd Wagner]

There is another snapshot (squirrelsqlfx-snapshot-20150428_2201.zip) that improves the error message. It does not fix the problem yet.

Could you please reproduce the error and post the new log.

Thanks
Gerd

[Nick]

Hi,

ok, I have attached the new improved error log.

Thank you for your great work BTW :-)

Regards
Nicola

[Gerd Wagner]

Hi Nick,

here is the next one: squirrelsqlfx-snapshot-20150429_1719

This may fix the problem. Could you again please give it a try and let me know if it worked.

Thanks

Gerd

[Nick]

Hi Gerd,

I can confirm you that the problem is fixed now. Good job :-)
Now the new Squirrel FX starts to be in good shape.

If I can report a "related" problem: the memory use of Squirrel FX grows rapidly, and there is no garbage cleaner button, as there is in the "old" Squirrel.

Thank you
Nick

[Gerd Wagner]

Nick,

thanks for your feedback. I close this bug.

Concerning the memory problem I confirm there is a memory problem. Could you please file a new bug for this issue.

For your information:
Another developer has already announced to be interested in fixing the memory issue.

Gerd