1. 16 Jun, 2021 1 commit
  2. 15 Jun, 2021 1 commit
  3. 11 Jun, 2021 2 commits
  4. 09 Jun, 2021 1 commit
  5. 08 Jun, 2021 6 commits
  6. 28 May, 2021 3 commits
  7. 27 May, 2021 2 commits
  8. 26 May, 2021 7 commits
  9. 25 May, 2021 4 commits
    • Carlos Garnacho's avatar
      libtracker-data: Do not delete full FTS row · 8e6ca66b
      Carlos Garnacho authored
      This might be nice for an optimization, we however go over all related
      classes and properties (incl. FTS) down the path, so it ends up just
      being repeated work.
      8e6ca66b
    • Carlos Garnacho's avatar
      libtracker-data: Only issue FTS updates where we mean to · 396cc9ee
      Carlos Garnacho authored
      Right now, getting the old values for a FTS property means those
      values are deleted, and a FTS update is issued afterwards (even if
      with empty strings).
      
      We don't strictly want to do that from all paths, only from those
      that are changing (i.e. not deleting) the FTS property value. Since
      the FTS5 machinery is getting extremely picky, it is better to
      avoid these needless roundtrips.
      396cc9ee
    • Carlos Garnacho's avatar
      libtracker-data: Mark specific properties as being deleted · 5717bd33
      Carlos Garnacho authored
      When dealing with single-valued properties that are deleted,
      we rely on the batch being explicitly flushed so that property
      deletions and insertions are not mixed up. We don't need to do this,
      instead we can tag individual properties as being deleted, so that
      we can mix deletions and insertions in the same row update.
      
      We were failing to do this explicit flushing at places in
      update_resource() which was leading to some triples being ignored
      (deemed as being deleted too, despite them being actually on their
      way to insertion).
      
      The tip of the iceberg here was a FTS property, as this
      circumstance left the real table column content and the fts5
      contentless tokenization data for that corresponding column out
      of sync. This resulted in FTS corrupted index on tracker-miner-fs-3
      after:
      
       $ touch ~/lalala
       $ rm ~/lalala
       $ tracker3 search lalala
      
      Making property deletion a per-property thing, we can avoid the
      explicit flush, write correctly the missing properties (nfo:fileName
      in the tracker:FileSystem graph, in this case), and make the column
      content match the FTS tokens again.
      
      Fixes: #308
      5717bd33
    • Nitin Wartkar's avatar
      docs: Add tracker_sparql_connection_query_statement() example · 6e1315ae
      Nitin Wartkar authored
      Using tracker_sparql_connection_query_statement() instead of tracker_sparql_connection_query()
      can increase the performance as it gets parsed only once when we ran it multiple times.
      
      Fixes: #128
      6e1315ae
  10. 23 May, 2021 10 commits
  11. 20 May, 2021 3 commits