On 21/08/14 10:39, Philip Van Hoof wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martyn,
The problem is that I that I think that with the journal disabled, the
ontology change coping code will detect this change and will exit the
tracker-store process instead of continuing.
Good poi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martyn,
The problem is that I that I think that with the journal disabled, the
ontology change coping code will detect this change and will exit the
tracker-store process instead of continuing.
Kind regards,
Philip
On 21/08/2014 11:20, Martyn R
On 08/08/14 10:55, Philip Van Hoof wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
How to implement this would go like this:
Hi Philip,
Thanks for the email here, allow me to respond :)
- - Detect the change with nao:lastModified and the existing
introspection ontology (tooling for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
How to implement this would go like this:
- - Detect the change with nao:lastModified and the existing
introspection ontology (tooling for this is available because of the
existing support)
- - Store the pending change (tooling available)
- - Make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martyn,
You have to be more careful about ontology changes:
https://git.gnome.org/browse/tracker/commit/?id=6b2dff6e18bd9a9d4238557b2dce2565fea49491
Maxcardinality changes are not supported by our ontology change coping
mechanism:
https://wiki.gnom
