Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <1962999116.1124376114838.JavaMail.jira@ajax.apache.org>
Date: Thu, 18 Aug 2005 16:41:54 +0200 (CEST)
From: "Fernanda Pizzorno (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-517) RecordSet - relative(int rows) behaves
 different in embedded and client/server mode when the positioning before the
 first row or after the last row.
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

RecordSet - relative(int rows) behaves different in embedded and client/server mode when the positioning before the first row or after the last row.
----------------------------------------------------------------------------------------------------------------------------------------------------

         Key: DERBY-517
         URL: http://issues.apache.org/jira/browse/DERBY-517
     Project: Derby
        Type: Bug
  Components: Network Client  
    Reporter: Fernanda Pizzorno
 Assigned to: Fernanda Pizzorno 


RecordSet - relative(int rows) behaves different in embedded and client/server mode when the positioning before the first row or after the last row.

The embedded driver shows the behaviour described in the JDBC 3.0 specification, returning false and postitioning in either before first or after last. While the client/server driver returns true and incrementing/decrementing the current row by "rows" and not setting the position to either before first of after last.

I have run a test with a result set with 10 rows, where I positioned in row 5 and moved +20 and - 20 using relative(int rows). With the embedded driver the method returned false, the current row was set to 0 and isAfterLast() and isBeforeFirst() returned true (for +20 and -20 respectively). With the client/server driver the method returned true, the current row was set to 25 and -15 (for +20 and -20 respectively) and isAfterLast() and isBeforeFirst() returned false.

I have also run a test as the first one but running next() 5 times instead of absolute(5) for postitioning in row 5, and then relative(20) produced the expected results with the client/server driver.

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