I tried your query tonight, Igor, and it worked, not that I understand how... the recursive query syntax is still a mystery to me and the many NOTs are a challenge to interpret. Compared to the FTS solution, I observe some preliminary differences in performance that are interesting.
The content being searched is made up from many tables. For the FTS search it is all inserted into the FTS4 virtual table which automatically builds the FTS index. For your recursive search, I create a VIEW of the same content. With larger databases, the time taken to build the FTS virtual table grows much faster than the VIEW. On the other hand, the time taken to search grows much faster for the recursive search than for the FTS. The search expression had three terms ANDed (a AND b AND c). I was delighted with having NOT, AND, OR operators in FTS among other capabilities. To incorporate all three in the recursive search is non-obvious. Tom -- View this message in context: http://sqlite.1065341.n5.nabble.com/WHERE-expression-with-operators-from-text-functions-tp78653p78700.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
