You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@metamodel.apache.org by "Kasper Sørensen (JIRA)" <ji...@apache.org> on 2015/11/05 08:54:27 UTC

[jira] [Commented] (METAMODEL-206) JDBC Datasets are TYPE_FORWARD_ONLY

    [ https://issues.apache.org/jira/browse/METAMODEL-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991283#comment-14991283 ] 

Kasper Sørensen commented on METAMODEL-206:
-------------------------------------------

I would in deed not classify this as a bug, but a design choice - for now at least.

I am actually not aware of any dataset implementations where you can start over. Can you give any examples? The DataSet interface doesn't reveal any methods to do so, so I would be surprised if it is somehow possible. Maybe _that_ is a bug, haha ;-)

> JDBC Datasets are TYPE_FORWARD_ONLY
> -----------------------------------
>
>                 Key: METAMODEL-206
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-206
>             Project: Apache MetaModel
>          Issue Type: Bug
>    Affects Versions: 4.4.1
>            Reporter: Geraud Campion
>            Priority: Minor
>
> Many of the other DataContext's Datasets allow you to iterate through the dataset multiple times. However, JDBCDataContext only allows you to do this once.  To workaround, I can reexecute the query before iterating the second time.
> I believe this is caused by executing statements using ResultSet.TYPE_FORWARD_ONLY. This may not actually be a bug. I am not sure if this is by design to provide better performance and ensure concurrency.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)