db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1322) Missing resets of isOnInsertRow state in net client when navigating away via other than ResultSet#next
Date Fri, 12 May 2006 13:06:08 GMT
Missing resets of isOnInsertRow state in net client when navigating away via other than ResultSet#next
------------------------------------------------------------------------------------------------------

         Key: DERBY-1322
         URL: http://issues.apache.org/jira/browse/DERBY-1322
     Project: Derby
        Type: Bug

  Components: JDBC, Network Client  
    Versions: 10.2.0.0    
    Reporter: Dag H. Wanvik
    Priority: Minor
     Fix For: 10.2.0.0


Please see the enclosed repro program.

When attempting the deleteRow, it will fail with SQL state 24000 "no
current row", since the first() call doesn't properly reset the
IsOnInsertRow_ state. By inspection of ../am/ResultSet.java I found
the other positioning calls beside next and moveToCurrentRow to suffer
the same problem.



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