Parliament could theoretically provide this information, as it maintains
statements in a monotonically increasing statement table (it doesn't as of
yet reuse the space freed when deleting statements).  Practically, however,
it would probably require a good amount of work to expose it.

Also, although I don't know that any implementations exist, a store with
triple/quad level MVCC could provide revision history (including the
statements added in the last transaction).

-Stephen


On Fri, Oct 28, 2011 at 8:27 AM, Laurent Pellegrino <
[email protected]> wrote:

> Thanks to all and especially Andy for pointing me to this paper :)
>
> Laurent
>
> On Fri, Oct 28, 2011 at 1:31 PM, Andy Seaborne <[email protected]> wrote:
> > On 26/10/11 08:39, Dave Reynolds wrote:
> >>
> >> On Tue, 2011-10-25 at 21:38 +0200, Laurent Pellegrino wrote:
> >>>
> >>> Hi all,
> >>>
> >>> Is it possible to retrieve the last N quadruples which have been
> >>> inserted into a Jena TDB datastore when the quadruples which have been
> >>> inserted do not contain any information about their publication time
> >>> (e.g. a jena built-in function to use in order to order by using the
> >>> internal identifiers used by the repository)?
> >>
> >> I don't believe there is such an insert timestamp available.
> >
> > There is no such timestamp.
> >
> > There was a paper at ISWC2011 that suggested using timestamps on
> something
> > (e.g. B+Tree blocks) to guide caching. [1]
> >
> > But as Greg (The presenter) said, "it cuts through every layer of
> > abstraction in a system to provide that information." and various
> > implementers in the audience smirked.
> >
> > So a system derived from TDB to add it maybe done by someone who s'
> > interested.  Also, for most users, it would be a noticable cost.
> >
> >        Andy
> >
> >
> > [1]
> > Enabling fine-grained HTTP caching of SPARQL query results
> > Gregory Todd Williams and Jesse Weave
> >
> >
> http://iswc2011.semanticweb.org/fileadmin/iswc/Papers/Research_Paper/03/70310752.pdf
> >
> >>
> >> Dave
> >>
> >>
> >
> >
>

Reply via email to