db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-276) ResultSet.relative(int row) cannot be called when the cursor is not positioned on a row.
Date Thu, 30 Jun 2005 21:03:57 GMT
     [ http://issues.apache.org/jira/browse/DERBY-276?page=all ]

Daniel John Debrunner updated DERBY-276:
----------------------------------------

    Fix Version: 10.2.0.0
    Description: 
If the cursor is not positioned on a row, calling ResultSet.relative() causes the following
exception:

Exception in thread "main" ERROR X0X87: ResultSet.relative(int row) cannot be called when
the cursor is not positioned on a row.
        at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:301)
        at org.apache.derby.impl.sql.execute.ScrollInsensitiveResultSet.getRelativeRow(ScrollInsensitiveResultSet.java:336)
        at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(EmbedResultSet.java:366)
        at org.apache.derby.impl.jdbc.EmbedResultSet.relative(EmbedResultSet.java:1840)

However, The 1.4.2 Javadoc says:
Note: Calling the method relative(1)  is identical to calling the method next() and calling
the method relative(-1) is identical to calling the method previous(). (This is confirmed
by the JDBC 3.0 spec, ch. 14.2.2)

Since next() is valid, so should rs.relative(1) (and all other arguments, since a too large
value will position the
cursor after the last row, and a too low value will position it before the first).


  was:
If the cursor is not positioned on a row, calling ResultSet.relative() causes the following
exception:

Exception in thread "main" ERROR X0X87: ResultSet.relative(int row) cannot be called when
the cursor is not positioned on a row.
        at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:301)
        at org.apache.derby.impl.sql.execute.ScrollInsensitiveResultSet.getRelativeRow(ScrollInsensitiveResultSet.java:336)
        at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(EmbedResultSet.java:366)
        at org.apache.derby.impl.jdbc.EmbedResultSet.relative(EmbedResultSet.java:1840)

However, The 1.4.2 Javadoc says:
Note: Calling the method relative(1)  is identical to calling the method next() and calling
the method relative(-1) is identical to calling the method previous(). (This is confirmed
by the JDBC 3.0 spec, ch. 14.2.2)

Since next() is valid, so should rs.relative(1) (and all other arguments, since a too large
value will position the
cursor after the last row, and a too low value will position it before the first).


    Environment: 

Patch committed revision 208683.

> ResultSet.relative(int row) cannot be called when the cursor is not positioned on a row.
> ----------------------------------------------------------------------------------------
>
>          Key: DERBY-276
>          URL: http://issues.apache.org/jira/browse/DERBY-276
>      Project: Derby
>         Type: Improvement
>   Components: JDBC
>     Reporter: Bernt M. Johnsen
>     Assignee: Bernt M. Johnsen
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: DERBY-276-V2.diff
>
> If the cursor is not positioned on a row, calling ResultSet.relative() causes the following
exception:
> Exception in thread "main" ERROR X0X87: ResultSet.relative(int row) cannot be called
when the cursor is not positioned on a row.
>         at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:301)
>         at org.apache.derby.impl.sql.execute.ScrollInsensitiveResultSet.getRelativeRow(ScrollInsensitiveResultSet.java:336)
>         at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(EmbedResultSet.java:366)
>         at org.apache.derby.impl.jdbc.EmbedResultSet.relative(EmbedResultSet.java:1840)
> However, The 1.4.2 Javadoc says:
> Note: Calling the method relative(1)  is identical to calling the method next() and calling
the method relative(-1) is identical to calling the method previous(). (This is confirmed
by the JDBC 3.0 spec, ch. 14.2.2)
> Since next() is valid, so should rs.relative(1) (and all other arguments, since a too
large value will position the
> cursor after the last row, and a too low value will position it before the first).

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