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

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

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

Hudson commented on JENA-458:
-----------------------------

Integrated in Jena__Development_Test #647 (See [https://builds.apache.org/job/Jena__Development_Test/647/])
    Part of JENA-458.

Rework GraphTDB so that there is one class for graph views of the database.
Use as much of the machinery of ARQ general GraphView system while
still carrying around the necessary information for TDB SPARQL evaluation.

Graphs are still restricted to be within a transaction boundary. (Revision 1483446)

     Result = SUCCESS
andy : 
Files : 
* /jena/trunk/jena-tdb/src/main/java/com/hp/hpl/jena/tdb/TDBLoader.java
* /jena/trunk/jena-tdb/src/main/java/com/hp/hpl/jena/tdb/graph/BulkUpdateHandlerTDB.java
* /jena/trunk/jena-tdb/src/main/java/com/hp/hpl/jena/tdb/graph/TransactionHandlerTDB.java
* /jena/trunk/jena-tdb/src/main/java/com/hp/hpl/jena/tdb/solver/OpExecutorTDB.java
* /jena/trunk/jena-tdb/src/main/java/com/hp/hpl/jena/tdb/solver/QueryEngineTDB.java
* /jena/trunk/jena-tdb/src/main/java/com/hp/hpl/jena/tdb/solver/SolverLib.java
* /jena/trunk/jena-tdb/src/main/java/com/hp/hpl/jena/tdb/store/DatasetGraphTDB.java
* /jena/trunk/jena-tdb/src/main/java/com/hp/hpl/jena/tdb/store/GraphNamedTDB.java
* /jena/trunk/jena-tdb/src/main/java/com/hp/hpl/jena/tdb/store/GraphTDB.java
* /jena/trunk/jena-tdb/src/main/java/com/hp/hpl/jena/tdb/store/GraphTDBBase.java
* /jena/trunk/jena-tdb/src/main/java/com/hp/hpl/jena/tdb/store/GraphTriplesTDB.java
* /jena/trunk/jena-tdb/src/main/java/com/hp/hpl/jena/tdb/sys/TDBInternal.java
* /jena/trunk/jena-tdb/src/main/java/com/hp/hpl/jena/tdb/transaction/DatasetGraphTransaction.java
* /jena/trunk/jena-tdb/src/test/java/com/hp/hpl/jena/tdb/assembler/TestTDBAssembler.java
* /jena/trunk/jena-tdb/src/test/java/com/hp/hpl/jena/tdb/store/TestDatasetTDB.java

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