> On Oct 24, 2019, at 7:17 AM, Andy Seaborne <[email protected]> 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: >> https://github.com/apache/jena/commit/241060548a9fca777b7d40f1f216ae7ed930b20e >> Before Andy and I got TIM into the design it now has (multiple MVCC indexes >> connected transactionally) I did another design that _does_ use buffering of >> operations. Since we didn't go with it, we cut it out of the codebase, but >> the history is there if you find it useful. > > Cool - might be a good starting point for buffering. I had a need for a > buffering dataset, which keeps the change, makes find() work as if the change > happened but does not pass add/delete through until requested.
That's just what that code did, so it might be just what you want. ajs6f
