[Joel Rosi-Schwartz]

Hi,

There is once again an issue with the DE in 3.8.2. Unfortunately, it appears as if we are going backwards rather than forwards on this one 🙁

I have auto commit turned in my DE preferences. (It appears that this can only be set globally now.) When I connect to the database instance I once again do not have any tables listed. There is the same exception in the Eclipse log as we got before when running with auto commit turned on.

!ENTRY com.genuitec.eclipse.sqlexplorer 4 4 Sep 27, 2004 16:51:18.250
!MESSAGE Error retrieving tables for com.genuitec.eclipse.sqlexplorer.dbviewer.model.SchemaNode
!STACK 0
com.ibm.db2.jcc.c.SqlException: Invalid operation: result set closed
        at com.ibm.db2.jcc.c.rc.mb(rc.java:3419)
        at com.ibm.db2.jcc.c.rc.c(rc.java:290)
        at com.ibm.db2.jcc.c.rc.next(rc.java:277)
        at net.sourceforge.squirrel_sql.fw.sql.SQLDatabaseMetaData.getTables(SQLDatabaseMetaData.java:640)
        at com.genuitec.eclipse.sqlexplorer.dbviewer.model.AbstractSchemaCatalogNode.fastLoad(Unknown Source)
        at com.genuitec.eclipse.sqlexplorer.sessiontree.model.SessionTreeNode.initializeDatabaseModel(Unknown Source)
        at com.genuitec.eclipse.sqlexplorer.sessiontree.model.SessionTreeNode.<init>(Unknown Source)
        at com.genuitec.eclipse.sqlexplorer.sessiontree.model.SessionTreeModel.createSessionTreeNode(Unknown Source)
        at com.genuitec.eclipse.sqlexplorer.sessiontree.actions.RetrievingTableDataProgress$RetrieveData.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

[Riyad Kalla]

Joel,
Did you mean 3.8.2? If not, can you give that a try and see if it works.

[Joel Rosi-Schwartz]

Yup 3.8.2. Sorry for confusion, I was in too much of a hurry.

– joel

[Riyad Kalla]

I sent this off to Jeff to take a look, thanks for the heads up.

[support-jeff]

Joel –

Please try the following steps:

1. Select the connection profile in the browser
2. Edit that profile (right-click and select edit, or use the view toolbar)
3. Check the box that reads “Prompt for Password”
4. Now when you try to open a connection on that profile, you will get the standard login dialog, where you can turn off auto-commit for each and every connection attempt.

The “Prompt for Password” was an enhancement added for 3.8.2 to allow the 99% of us who want to be completely insecure and have DE store our passwords for us and not ask every time. It is unchecked by default; probably should have been checked, but oh well.

I still have an enhancement request in for adding an auto-commit checkbox to the profile edit screen so that you can turn it off at that level as well.

[Joel Rosi-Schwartz]

Jeff,

Yes that works. Oddly the password dialog comes up with the proper defaults as I have them set in the preferences, i.e. auto commit disabled and commit on close enabled. If I revert to automatic login then it falls apart again. So it looks like your code is not handling the preferences properly in the use case where “Prompt for Password” is disabled.

While I was really looking forward to not having to go through the password dialog all of the time, I can certainly live with this a while longer. Thanks for the diagnosis.

– joel

[support-jeff]

Arghghghghg! So sorry. Thank you for finding this bug. Yet another test case to add! Glad that the work-around will work for you for now.

[Author]

Posts