[
https://issues.apache.org/jira/browse/CASSANDRA-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041832#comment-13041832
]
Rick Shaw commented on CASSANDRA-2725:
--------------------------------------
And finally for our "Bonus Round"...
The row navigation methods (previous, absolute, afterFirst, etc)while optional
as far as the semantics are concerned, are trivial to implement given that all
the necessary artifacts are already available in the {{CResultSet}} Class.
I propose that these be treated as the above methods and deleted from
{{AbstractResultSet}} class and added back into {{CResultSet}} class and
implemented as appropriate.
This encompasses the following methods:
- {{absolute(int index)}}
- {{afterLast()}}
- {{beforeFirst(int index)}}
- {{first(int index)}}
- {{previous(int index)}}
- {{relative(int index)}}
I'm fine either way but this is a leadership call.
> Update the JDBC semantics contained in the class AbstractResultSet
> ------------------------------------------------------------------
>
> Key: CASSANDRA-2725
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2725
> Project: Cassandra
> Issue Type: Improvement
> Components: API
> Affects Versions: 0.8.0 beta 2
> Reporter: Rick Shaw
> Priority: Minor
> Labels: cql, jdbc
> Fix For: 0.8.1
>
>
> The {{AbstractResultSet}} cleverly isolates all the methods that are not
> planned to be implemented in the next release of of the JDBC Result Set
> implemented by the class {{CResultSet}}. This improvement will tighten the
> JDBC semantics for this set of methods.
> This improvement is related to
> [CASSANDRA-2720|https://issues.apache.org/jira/browse/CASSANDRA-2720] but is
> not blocked by it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
