db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Wilder (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server
Date Thu, 09 Jun 2005 18:20:19 GMT
     [ http://issues.apache.org/jira/browse/DERBY-213?page=all ]

Philip Wilder updated DERBY-213:
--------------------------------

    Attachment: DERBY-213_6_9_2005.txt

IRC chat transcript June, 9 2005
#########################
Summary:

* Noted Philip's first contribution to Derby Source (DERBY-343).
* Addressed the importance of signing an Individual Contributor License Agreement.
* Discussed Modifications to the resultset.java test class. Tests now check the functionality
of statements that have a maximum number of rows set with the java.sql.Statement.setMaxRows(int)
method and report how many rows were returned by a ResultSet.
* Discussed the test failures caused by potential patch for Derby-213. Came to the conclusion
that the test failures were likely harmless but assigned Philip the task of comparing the
new DerbyNetClient .out files against the Embedded .out files for verification.
* Reviewed Client/Server interaction and discovered that DRDAStatement.setMaxRows() functionality
is handled only on the client side. Searched DRDA specs to find any evidence to the contrary
to no success. Determined this is an issue that could use more analysis (later deciding to
open a Jira Issue about it).
* Toyed with the idea of assigning Philip the task of running StmtCloseFunTest.java against
the DerbyNetClient Framework with the proposed modifications but eventually rejected it on
the ground that this test is already run under the derbyall testsuite.
* Assigned tasks and agreed upon next meeting time.

> ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network
Server
> --------------------------------------------------------------------------------------------------
>
>          Key: DERBY-213
>          URL: http://issues.apache.org/jira/browse/DERBY-213
>      Project: Derby
>         Type: Bug
>   Components: Network Server
>     Versions: 10.1.0.0
>     Reporter: Kathey Marsden
>     Assignee: Philip Wilder
>  Attachments: Client.java, Create.java, DERBY-213_6_9_2005.txt, DERBY-213_irc_6_3_2005,
DERBY-213_irc_6_7_2005.txt, DERBY-213_irc_6_8_2005, IRCTranscript_June2_2005.txt, Server.java,
resultset.java
>
> Network Server closes the result set if ResultSet.next() is 
> called after the last row of the result set.  The test code 
> below throws the following exception.
> SQLState:   null
> Severity: -99999
> Message:  Invalid operation: result set closed
> com.ibm.db2.jcc.am.SqlException: Invalid operation: result set 
> closed
>         at 
> com.ibm.db2.jcc.am.ResultSet.checkForClosedResultSet(ResultSet.j
> ava:3419)
>         at 
> com.ibm.db2.jcc.am.ResultSet.nextX(ResultSet.java:290)
>         at 
> com.ibm.db2.jcc.am.ResultSet.next(ResultSet.java:277)
>         at AfterLast.test(AfterLast.java:75)
>         at AfterLast.main(AfterLast.java:32)
> stmt.executeUpdate("CREATE  TABLE TAB ( I INT)");
> stmt.executeUpdate("INSERT INTO TAB VALUES(1)");
> stmt.executeUpdate("INSERT INTO TAB VALUES(2)");
> String sql ="SELECT * from tab";		
> ps = conn.prepareStatement(sql);
> ResultSet rs = ps.executeQuery();
> System.out.println(sql);
> while (rs.next())
> System.out.println(rs.getInt(1));
> try {
> 	System.out.println("one more next");
> 	rs.next();
> 		}
>     catch (Exception e)
> 		{
> 		System.out.println("FAIL: next should return false not throw 
> exception");
> 		e.printStackTrace();
> 		}

-- 
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


Mime
View raw message