On 25/10/2019 16:02, ajs6f wrote:
On Oct 24, 2019, at 7:17 AM, Andy Seaborne wrote:
On 23/10/2019 15:31, ajs6f wrote:
Hi Dick!
I'm afraid the answer for TDB2 and TIM is no, not out of the box. Both use MVCC
techniques, not buffering operations. Andy can tell you about TDB1.
This might
> On Oct 24, 2019, at 7:17 AM, Andy Seaborne wrote:
>
> On 23/10/2019 15:31, ajs6f wrote:
>> Hi Dick!
>> I'm afraid the answer for TDB2 and TIM is no, not out of the box. Both use
>> MVCC techniques, not buffering operations. Andy can tell you about TDB1.
>> This might (maybe) be helpful:
>>
TDB2 recently got TransactionListener to tap into the transaction
lifecycle.That was for a specific need (for abort to undo some changes
made ahead of time) but the idea might be general.
In RDF Delta, there is DatasetGraphChanges whch enables you to get
changes, which includes begin-commit.
Hi Dick!
I'm afraid the answer for TDB2 and TIM is no, not out of the box. Both use MVCC
techniques, not buffering operations. Andy can tell you about TDB1.
This might (maybe) be helpful:
https://github.com/apache/jena/commit/241060548a9fca777b7d40f1f216ae7ed930b20e
Before Andy and I got TIM
Hi.
Is it possible to natively detect whether a write has occurred to a
DatasetGraph since a particular epoch?
For the purposes of caching if I perform an expensive read from a
DatasetGraph knowing whether I need to invalidate the cache is very useful.
Does TDB or the Mem natively track if a
