424165 2020-07-13 17:40:26 +0000 Negated terms in queries 2025-03-14 04:23:20 +0000 1 1 3 Frameworks and Libraries frameworks-baloo general unspecified Other Linux CONFIRMED NOR normal --- 1 vini.ipsmaker stefan.bruens j.straight-kde nate pat_h tagwerk19 0 oldest_to_newest 1943506 0 vini.ipsmaker 2020-07-13 17:40:26 +0000 Nepomuk's Query class allowed construction from a manually created Term object. This setup allowed one to use the negation basic logic operator. Baloo's Query dropped the possibility to feed a manually created Term object and moved Term to implementation details. However, in doing so, it also dropped support for such operator (only AND and OR are supported). Negation is a basic logic operator and should be supported. My use case is very simple. Every time I read a document, I tag it with "already-read". I want to search for every document in the tag "project1" that isn't tagged as "already-read". Baloo's Term class still retains the "negated" property. I believe one only needs to update the function Term::fromVariantMap() and it'll automatically propagate to a few upper classes and functions such as Query::fromJSON(). 1943522 1 nate 2020-07-13 18:14:46 +0000 Sounds like you're pretty close to writing a patch for this. :) Wanna go all the way and submit one? https://invent.kde.org/frameworks/baloo/-/merge_requests 1943542 2 stefan.bruens 2020-07-13 19:02:47 +0000 Its not only the query which has to be updated, it also has to be executed. Thats the non-trivial part. 1950851 3 vini.ipsmaker 2020-08-14 21:55:01 +0000 > Sounds like you're pretty close to writing a patch for this. :) Wanna go all the way and submit one? I thought more about the problem and -- as Stefan Brüns pointed out -- the query processor will have to be upgraded too. Old Nepomuk would rely on OpenLink Virtuoso for query execution, so no code from old code base could be used as a reference in the new Baloo framework. I'll just find a workaround for my use-case. 2265329 4 stefan.bruens 2023-11-13 08:48:51 +0000 *** Bug 474994 has been marked as a duplicate of this bug. *** 2407455 5 john 2025-03-14 04:23:20 +0000 *** Bug 500414 has been marked as a duplicate of this bug. ***