You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bernt M. Johnsen (JIRA)" <de...@db.apache.org> on 2005/06/29 13:09:00 UTC
[jira] Created: (DERBY-403) NetworkClient closes resultset when next() moves the cursor beyond the last row
NetworkClient closes resultset when next() moves the cursor beyond the last row
-------------------------------------------------------------------------------
Key: DERBY-403
URL: http://issues.apache.org/jira/browse/DERBY-403
Project: Derby
Type: Bug
Components: Network Client
Reporter: Bernt M. Johnsen
NetworkClient closes resultset when next() moves the cursor beyond the last row
The following stub will work in EmbeddedDriver but not in NetworkClient:
while (rs.next()) {
}
rs.getMetaData();
In NetworkCLient, you get:
Exception in thread "main" org.apache.derby.client.am.SqlException: Invalid operation: result set closed
at org.apache.derby.client.am.ResultSet.checkForClosedResultSet(ResultSet.java:3269)
at org.apache.derby.client.am.ResultSet.getMetaDataX(ResultSet.java:1386)
at org.apache.derby.client.am.ResultSet.getMetaData(ResultSet.java:1377)
This causes problems for Derby NetwokClient when used with SQuirreL (http://squirrel-sql.sourceforge.net/)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-403) NetworkClient closes resultset when next() moves the cursor beyond the last row
Posted by "Bernt M. Johnsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-403?page=all ]
Bernt M. Johnsen updated DERBY-403:
-----------------------------------
Description:
NetworkClient closes resultset when next() moves the cursor beyond the last row
The following stub will work in EmbeddedDriver but not in NetworkClient:
while (rs.next()) {
}
rs.getMetaData();
In NetworkCLient, you get:
Exception in thread "main" org.apache.derby.client.am.SqlException: Invalid operation: result set closed
at org.apache.derby.client.am.ResultSet.checkForClosedResultSet(ResultSet.java:3269)
at org.apache.derby.client.am.ResultSet.getMetaDataX(ResultSet.java:1386)
at org.apache.derby.client.am.ResultSet.getMetaData(ResultSet.java:1377)
1) this is not expected behaviour as I read the spec and the tutorial.
2) This causes problems for Derby NetwokClient when used with SQuirreL (http://squirrel-sql.sourceforge.net/)
was:
NetworkClient closes resultset when next() moves the cursor beyond the last row
The following stub will work in EmbeddedDriver but not in NetworkClient:
while (rs.next()) {
}
rs.getMetaData();
In NetworkCLient, you get:
Exception in thread "main" org.apache.derby.client.am.SqlException: Invalid operation: result set closed
at org.apache.derby.client.am.ResultSet.checkForClosedResultSet(ResultSet.java:3269)
at org.apache.derby.client.am.ResultSet.getMetaDataX(ResultSet.java:1386)
at org.apache.derby.client.am.ResultSet.getMetaData(ResultSet.java:1377)
This causes problems for Derby NetwokClient when used with SQuirreL (http://squirrel-sql.sourceforge.net/)
> NetworkClient closes resultset when next() moves the cursor beyond the last row
> -------------------------------------------------------------------------------
>
> Key: DERBY-403
> URL: http://issues.apache.org/jira/browse/DERBY-403
> Project: Derby
> Type: Bug
> Components: Network Client
> Reporter: Bernt M. Johnsen
>
> NetworkClient closes resultset when next() moves the cursor beyond the last row
> The following stub will work in EmbeddedDriver but not in NetworkClient:
> while (rs.next()) {
> }
> rs.getMetaData();
> In NetworkCLient, you get:
> Exception in thread "main" org.apache.derby.client.am.SqlException: Invalid operation: result set closed
> at org.apache.derby.client.am.ResultSet.checkForClosedResultSet(ResultSet.java:3269)
> at org.apache.derby.client.am.ResultSet.getMetaDataX(ResultSet.java:1386)
> at org.apache.derby.client.am.ResultSet.getMetaData(ResultSet.java:1377)
> 1) this is not expected behaviour as I read the spec and the tutorial.
> 2) This causes problems for Derby NetwokClient when used with SQuirreL (http://squirrel-sql.sourceforge.net/)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-403) NetworkClient closes resultset when next() moves the cursor beyond the last row
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-403?page=comments#action_12314675 ]
Kathey Marsden commented on DERBY-403:
--------------------------------------
This is a duplicate of DERBY-213 which Philip Wilder and I have been working on. Removing that close means that client has to be changed so that it handles autocommit properly upon statement completion and some other clarifications of the JDBC spec.
This subject is currently a topic of discussion on the developer list.
See:
http://mail-archives.apache.org/mod_mbox/db-derby-dev/200506.mbox/%3c42BC0C49.3030403@acadiau.ca%3e
> NetworkClient closes resultset when next() moves the cursor beyond the last row
> -------------------------------------------------------------------------------
>
> Key: DERBY-403
> URL: http://issues.apache.org/jira/browse/DERBY-403
> Project: Derby
> Type: Bug
> Components: Network Client
> Reporter: Bernt M. Johnsen
>
> NetworkClient closes resultset when next() moves the cursor beyond the last row
> The following stub will work in EmbeddedDriver but not in NetworkClient:
> while (rs.next()) {
> }
> rs.getMetaData();
> In NetworkCLient, you get:
> Exception in thread "main" org.apache.derby.client.am.SqlException: Invalid operation: result set closed
> at org.apache.derby.client.am.ResultSet.checkForClosedResultSet(ResultSet.java:3269)
> at org.apache.derby.client.am.ResultSet.getMetaDataX(ResultSet.java:1386)
> at org.apache.derby.client.am.ResultSet.getMetaData(ResultSet.java:1377)
> 1) this is not expected behaviour as I read the spec and the tutorial.
> 2) This causes problems for Derby NetwokClient when used with SQuirreL (http://squirrel-sql.sourceforge.net/)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-403) NetworkClient closes resultset when next() moves the cursor beyond the last row
Posted by "Bernt M. Johnsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-403?page=all ]
Bernt M. Johnsen closed DERBY-403:
----------------------------------
Resolution: Duplicate
Duplicate of DERBY-213
> NetworkClient closes resultset when next() moves the cursor beyond the last row
> -------------------------------------------------------------------------------
>
> Key: DERBY-403
> URL: http://issues.apache.org/jira/browse/DERBY-403
> Project: Derby
> Type: Bug
> Components: Network Client
> Reporter: Bernt M. Johnsen
>
> NetworkClient closes resultset when next() moves the cursor beyond the last row
> The following stub will work in EmbeddedDriver but not in NetworkClient:
> while (rs.next()) {
> }
> rs.getMetaData();
> In NetworkCLient, you get:
> Exception in thread "main" org.apache.derby.client.am.SqlException: Invalid operation: result set closed
> at org.apache.derby.client.am.ResultSet.checkForClosedResultSet(ResultSet.java:3269)
> at org.apache.derby.client.am.ResultSet.getMetaDataX(ResultSet.java:1386)
> at org.apache.derby.client.am.ResultSet.getMetaData(ResultSet.java:1377)
> 1) this is not expected behaviour as I read the spec and the tutorial.
> 2) This causes problems for Derby NetwokClient when used with SQuirreL (http://squirrel-sql.sourceforge.net/)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira