Re: [Tracker] Could not create FTS delete statement:

[Carlos Garnacho <carlosg gnome org>]

Hi Chris,

On Thu, Mar 2, 2017 at 3:24 PM, Chris <cpollock embarqmail com> wrote:
> Could someone be kind enough to tell me what this warning means? The
> complete line reads:
>
> Mar  2 08:20:18 localhost org.freedesktop.Tracker1[3934]: (tracker-
> store:4352): Tracker-WARNING **: Could not create FTS delete statement:
> table fts5 has no column named nco:hobby
> Mar  2 08:20:18 localhost org.freedesktop.Tracker1[3934]: (tracker-
> store:4352): Tracker-WARNING **: Could not create FTS delete statement:
> table fts5 has no column named nco:hobby

This started appearing in some systems due to a glitch in the change
from fts4 to fts5, tracker had to trigger a change in full-text
indexed fields, and nco:hobby was the innocent victim.

But it does seem like the file ~/.cache/tracker/ontologies.gvdb
(containing a cache of the current ontology) didn't get updated
properly in some cases, which means that tracker still deals with that
property as if it were fts-indexed, while it's no longer the case.

> I'm very sure it's harmless but as one who looks at his syslog closely
> its one of those petty annoyances that bites into my OCD that I know
> shouldn't be there.

You can get rid of it by doing:
tracker daemon -t
rm ~/.cache/tracker/ontologies.gvdb
tracker daemon -s

That should get that file rebuilt from scratch, containing the
up-to-date ontology. I would have liked to do something from the
Tracker side, but that requires yet another change in FTS fields, and
those happen rarely...

Cheers,
  Carlos