jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Created] (OAK-423) Query: org.apache.jackrabbit.oak.spi.query.Cursor.currentRow called too late
Date Mon, 05 Nov 2012 14:27:16 GMT
Thomas Mueller created OAK-423:
----------------------------------

             Summary: Query: org.apache.jackrabbit.oak.spi.query.Cursor.currentRow called
too late
                 Key: OAK-423
                 URL: https://issues.apache.org/jira/browse/OAK-423
             Project: Jackrabbit Oak
          Issue Type: Improvement
            Reporter: Thomas Mueller
            Assignee: Thomas Mueller


Some join conditions call currentRow() on a Cursor when the next() method already returned
false. This is wrong.

Now that we have IndexRow class, it would make sense to use Iterator<IndexRow> instead
of a separate Cursor class. I believe this would also solve the above problem, and possibly
would make the code easier to understand.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message