Re: [Squirrel-sql-users] derby access (was cloudscape)

[Gerd W. <bir...@t-...>]

Hi Xavier,

it looks like your driver closes a ResultSet when it was completely 
iterated through. SQuirreL tried to access the ResultSetMetaData after 
iterating. I was able to fix this. The fix is in CVS. If you want me to 
I could mail you a new version of squirrel-sql.jar (2.1 MB).

Still the exception will persist (as in 1.2beta6) because SQuirreL tries 
  to read SQL warnings from the ResultSet after iterating. This will 
fail when the ResultSet is closed.

Gerd


Xavier Vigouroux wrote:
> Hi,
> 
> Here is the log I get:
> 
> 
> ------------------------------------------------------------------------
> 
> org.apache.derby.client.am.SqlException: Invalid operation: result set closed
> 	at org.apache.derby.client.am.ResultSet.checkForClosedResultSet(ResultSet.java:2900)
> 	at org.apache.derby.client.am.ResultSet.getMetaDataX(ResultSet.java:1240)
> 	at org.apache.derby.client.am.ResultSet.getMetaData(ResultSet.java:1232)
> 	at net.sourceforge.squirrel_sql.fw.datasetviewer.ResultSetMetaDataDataSet.getMetaDataFromResultSet(ResultSetMetaDataDataSet.java:238)
> 	at net.sourceforge.squirrel_sql.fw.datasetviewer.ResultSetMetaDataDataSet.<init>(ResultSetMetaDataDataSet.java:92)
> 	at net.sourceforge.squirrel_sql.client.session.mainpanel.SQLResultExecuterPanel$SQLExecutionHandler.sqlResultSetAvailable(SQLResultExecuterPanel.java:733)
> 	at net.sourceforge.squirrel_sql.client.session.SQLExecuterTask.processResultSet(SQLExecuterTask.java:450)
> 	at net.sourceforge.squirrel_sql.client.session.SQLExecuterTask.processQuery(SQLExecuterTask.java:359)
> 	at net.sourceforge.squirrel_sql.client.session.SQLExecuterTask.run(SQLExecuterTask.java:252)
> 	at net.sourceforge.squirrel_sql.fw.util.TaskExecuter.run(TaskExecuter.java:82)
> 	at java.lang.Thread.run(Thread.java:536)
> 
> 
> ------------------------------------------------------------------------
> 
> 
> 
> What is strange is that I disable "show SQL Result metadata" in the 
> connecteciot nproperties but it doesn't help.
> 
> ps: note that I also send a mail concerning this problem to derby DB ML.
> 
> thanks
> 
> Le 28 juin 05, à 20:35, Gerd Wagner a écrit :
> 
>> Hi Xavier,
>>
>> could you have look at the SQuirreL logs (Menu Windows -->View 
>> SQuirreL logs). There you should find a stacktrace of your exception. 
>> Could you please post the stacktrace together with your request.
>>
>> Thanks
>>
>> Gerd
>>
>> Xavier Vigouroux wrote:
>>
>>> Hi,
>>> I try to connect to a derby database, I have a different behavior  
>>> SQL requests withfrom 1.2beta6 to 2.0rc1:
>>> o in 1.2beta6: I can execute select, get an exception 
>>> (org.apache.derby.client.am.SqlException: invalid operation: result 
>>> set closed) but can see the result of the request
>>> o in 2.0rc1: I have the same exception but with no result.
>>> what must I investigate to get better insight.
>>> XFV
>>
>>
>>