>> However, before it could be suitable as a possible replacement, it will
>> likely require more optimization. Some queries, especially more complex
>> ones, are slower than the equivalent searches and agendas in the current
>> Org Agenda code. This is because of the way the queries run predicates
>> on each heading. Despite the current Org Agenda code's complexity, it
>> is well optimized and hard to beat.
>
> Are you saying that queries are turned into regexp searches within Org
> files? If so, I don't think they should.
>
> Queries should only operate on the output of the data extraction,
> possibly a list of defstructs. I.e., you first extract all meaningful
> data from the document (during idle time, with cache, or whatever
> optimization would be chosen), store it in an appropriate format, then
> query it.
>
I think the same way. In some language library like Clojure's enlive
handle the HTML string the same way.
--
[ stardiviner ] don't need to convince with trends.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
