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

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Done
• Affects Version/s: TDB 0.10.1
• Fix Version/s: Jena 3.6.0
• Component/s: TDB
• Assignee: Andy Seaborne
• Reporter: Andy Seaborne
• Created: 16/May/13 16:59
• Updated: 17/Dec/17 19:46
• Resolved: 04/Dec/17 14:16

Description

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.