Hi Andy My tattered recollection is that originally there was only GraphTripleStore (and NodeToTriplesMap). Then we (for some value of "we") realised that the code made assumptions that were false for non-memory (so, at the time, RDB) triples, so the existing code was renamed to have a Mem suffix and the non-Mem code had the assumptions removed.
Alas, I cannot recall what the assumptions were ... maybe to do with whether the value of a literal was always there (in the Mem case) or not (in the non-Mem case). I suspect then changes were made to non-Mem code that could have been, but were not, shared with Mem code. I don't think we can simply eliminate the left-hand classes in favour of the right-hand ones in case there's code which (explicitly or implicitly) expects the Mem classes. I have another look tomorrow. Chris On 9 July 2017 at 14:08, Andy Seaborne <[email protected]> wrote: > Chris, > > I'm engaged in some code-archaeology :-) (after looking at the message > about Delta which I'm kind of lost on). I'm hoping you can recall what the > situation is for some classes. > > GraphMem uses GraphTripleStoreMem. > > But there are some classes that look quite similar: > > GraphTripleStore -- GraphTripleStoreMem > NodeToTriplesMap -- NodeToTriplesMapMem > > (are there any others of this kind?) > > Are the left-hand ones replaced by the right-hand ones? > > The left-hand ones have some tests - the right-hand ones don't have direct > tests although given that they are behind GraphMem, they get a lot of tests > anyway. > > Andy > -- "What I don't understand is this ..." Trevor Chaplin, /The Beiderbeck Affair/ Epimorphics Ltd, http://www.epimorphics.com Registered address: Court Lodge, 105 High Street, Portishead, Bristol BS20 6PT Epimorphics Ltd. is a limited company registered in England (number 7016688)
