[jira] [Resolved] (JENA-458) Make model work across transaction boundaries / make model.begin do something reasonable.

["Andy Seaborne (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JENA-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Seaborne resolved JENA-458.
--------------------------------

    Resolution: Fixed
      Assignee: Andy Seaborne
    
> Make model work across transaction boundaries / make model.begin do something reasonable.
> -----------------------------------------------------------------------------------------
>
>                 Key: JENA-458
>                 URL: https://issues.apache.org/jira/browse/JENA-458
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: TDB
>    Affects Versions: TDB 0.10.1
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Minor
>
> Currently, the model view must be re-feteched from the TDB dataset across transaction boundaries even if all updates went via the model.
> For some models, this is expensive - for example, inference models with significant forward chaining.
> A problem will always be that if the database can change via a different route.
> A side-effect will be that model.begin()/model.commit()/model.abort() can be implemented as always being a write transaction.  It would need an API change to support the difference between read and write.

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