1. 05 Feb, 2019 1 commit
  2. 02 Feb, 2019 2 commits
  3. 31 Jan, 2019 1 commit
  4. 29 Jan, 2019 1 commit
  5. 27 Jan, 2019 1 commit
  6. 26 Jan, 2019 1 commit
  7. 25 Jan, 2019 1 commit
  8. 24 Jan, 2019 1 commit
    • Andrea Azzarone's avatar
      tracker-monitor: Prevent stack smashing · 63c0a5d4
      Andrea Azzarone authored
      Make sure to use GPOINTER_TO_UINT when using g_hash_table_lookup_extended() to
      prevent stack smashing. This will make sure that in the architectures where
      sizeof(GFileMonitorEvent) < sizeof(gpointer), g_hash_table_lookup_extended()
      will not write more bytes than prev_event_type can hold.
      Fixes: #71
  9. 20 Jan, 2019 1 commit
  10. 19 Jan, 2019 1 commit
  11. 18 Jan, 2019 1 commit
  12. 17 Jan, 2019 2 commits
  13. 13 Jan, 2019 3 commits
  14. 12 Jan, 2019 2 commits
  15. 08 Jan, 2019 1 commit
  16. 07 Jan, 2019 1 commit
    • Sam Thursfield's avatar
      ci: Update container image URL · db42ec3f
      Sam Thursfield authored
      The container image used for CI is now built from a project in the
      gitlab.gnome.org/GNOME/ namespace, rather than my personal namespace.
  17. 05 Jan, 2019 5 commits
  18. 30 Dec, 2018 1 commit
  19. 26 Dec, 2018 8 commits
    • Fabio Tomat's avatar
      Update Friulian translation · 8ca9d930
      Fabio Tomat authored
    • Carlos Garnacho's avatar
      tests: Add a bunch of property path tests · 7e09abe1
      Carlos Garnacho authored
      Alternative, recursive, optional paths are tested, and combinations
      of those.
    • Carlos Garnacho's avatar
      libtracker-data: Implement alternative path sequences · 0d5c1a65
      Carlos Garnacho authored
      The alternative path operator '|' allows multiplexing the ways to get a
      value. For example:
        { ?u nie:title|nfo:fileName 'foo' }
      will return elements whose title or filename matches the given string.
    • Carlos Garnacho's avatar
      libtracker-data: Implement PathMod · 862b1617
      Carlos Garnacho authored
      All three modifiers in PathMod are implemented now:
        - ?(zero or one): { ?u nfo:belongsToContainer? ?c } returns direct
          children of ?c, plus ?c itself.
        - *(zero or more): { ?u nfo:belongsToContainer* ?c } returns all children
          of ?c recursively, including ?c itself.
        - +(one or more): { ?u nfo:belongsToContainer+ ?c } returns all children
          of ?c recursively.
    • Carlos Garnacho's avatar
      libtracker-data: Handle current path operators through WITH clause · 0b80cc61
      Carlos Garnacho authored
      Using the WITH clause is already a pre-requisite for * and + operators
      (as those queries need to be recursive). It then struck me that using
      it for all path operators is simpler and easier to read both in code and
      SQL, for starters:
        - We were going long ways to invert the processing order of VerbPath and
          ObjectList, so the latter would be handled within the former. This was
          necessary so we could eg. invert subject and object in ^.
        - Each property path element results in a rather simple SELECT in the
          WITH clause, and nesting those comes off naturally. This is handy as
          a property path is actually an expression tree, which we weren't
          handling that well.
      As a first step, add this infrastructure for property paths using the WITH
      clause and use it for the currently supported operators.
      We still fall through the usual code paths (no subqueries in WITH clause)
      if the property path is formed of a single literal with no operators
      (i.e. the good old "?s foo:bar ?o" case). This is still necessary for
      fts:match (which is not really a property, thus can't be used in property
      paths) and rdfs:domain special casing (which just applies if the predicate
      is a variable, not the case with property paths).
    • Carlos Garnacho's avatar
      tests: Shutdown data manager in tracker-sparql-test · 98f36a5a
      Carlos Garnacho authored
      The TrackerDataManagers were not properly shutdown, thus leaking memory
      and FDs. Adding more tests makes the latter noticeable.
    • Carlos Garnacho's avatar
      tests: Ensure ordering in property path tests · e3ac14b5
      Carlos Garnacho authored
      So we don't implicitly rely on the query/implementation underneath.
    • Carlos Garnacho's avatar
      libtracker-data: Gracefully exclude NULL subject/pred/object from resultset · 8433d386
      Carlos Garnacho authored
      This is mentioned in the spec, and was correctly handled in the previous
      parser (although the comment mentioned text from a similar restriction with
      CONSTRUCT). Solutions with unbound variables should simply be ignored,
      this was kinda the case but just detected through g_return_if_fail() later
  20. 20 Dec, 2018 1 commit
  21. 18 Dec, 2018 4 commits