Re: a sort of tail -f on Data.fs

On Thu, Oct 30, 2014 at 3:15 AM, Yuri <[email protected]> wrote:
> Il 29/10/2014 20:31, Sean Upton ha scritto:
>> Why not just watch the Undo tab in the ZMI for the root of the site?
>> This contains transaction history with dates and commit messages, and
>> usually paths to objects modified?
>
> This does not contain contents of objects and don't record, for example,
> catalogs objects. But it is a good starting point on where to look for (
> app._p_jar._storage.iterator(start=time_time_of_last_poll)  :-)

The problem, I suppose, is that knowing which objects were modified
could get either really noisy, or arbitrary -- as ZODB has no capacity
to track where objects are referenced (except for during pack of
certain storages like RelStorage).

One transaction may modify thousands of objects, many do.  The best
you might get is to maintain an index of OID to path for content
objects only, and then dig into a list of modified OIDs via the
transaction iterator interface to find matches.

OTOH, possibly having a tool to link transactions to the request log
entries that initiated them (e.g. Z2.log entry) could be useful, but I
have no idea how to provide a 1:1 link between the request and the
TID.

Sean

------------------------------------------------------------------------------