Skip to content

libtracker-sparql: Handle correctly backreferences in TrackerResource tree

Carlos Garnacho requested to merge wip/carlosg/handle-recursive-resources into master

We do keep a notion of already visited TrackerResources when generating the output. However that could go wrong if the TrackerResource references itself or a "parent" TrackerResource.

Add the resources to the done list beforehand, so they are ensured not to be visited again if such backreferences exist.

Related: tracker-miners#60 (closed)

Merge request reports