obsidian-query-control VS datascript

You might try the 6.0 version of the Query Control. The way it worked changed quite a while back. We can read about it in discussions on the GitHub page. I have version 6.0 which may work better. However, like Obsidian Search, it doesn't seem to automatically expand all results. If it could do that, it could show the content of notes in the list without having to manually expand each note.

If you use plugins you can extend the built-in search box: https://github.com/nothingislost/obsidian-query-control https://github.com/jplattel/obsidian-query-language

Don't want a plugin, use embed search. Need more customization? Obsidian Query Control If it doesn't scare you that it's in beta.

If you install the Obsidian Query Control plugin, you can click a button to show all the context lines just like you'd see if you performed a regular Obsidian Search.

Obsidian Query Control. MY GOD! WHY DID I NOT COME ACROSS THIS BEFORE!!!

A query can create a list of lines that match the query. A query is similar to Dataview. The Beta Obsidian Query Control can provide additional features. It's web page shows what a query looks like. A query can also return context lines below a line that contains the search term.

You just have to strip the natural language part. Fixed: https://github.com/nothingislost/obsidian-query-control

I agree with your issue of reification and I like the concept of a "wit."

I think we're getting there, too. See, for instance, https://github.com/nothingislost/obsidian-query-control — it renders the results of an embedded Obsidian query and you can interact with checkboxes. Likewise, a collaboration between dataview and the Task Collector plugin might let us manipulate different task statuses from a dataview query: https://github.com/ebullient/obsidian-task-collector/issues/...

Exciting times!

Hi pests, I don't think the criticism in the comments gives a full picture.

I wrote about a particular flavor of datalog, in common use today. [1] [2]. The earliest representation I know, which matches the syntax of my essay, was in SICP [3]

There's another, more academic form of datalog, which looks a lot more like prolog. Both have lots of similarities: both systems have a set of facts and rules. Both systems have can take a partially filled fact or rule, and find all matching facts. The more academic flavors of Datalog are useful for general logic, and particularly powerful for recursive questions. The variant I showed is more tailed for database queries.

[1] https://github.com/tonsky/datascript

There is also datascript as a similar option.

What's the use case for relic? Sounds similar to https://github.com/tonsky/datascript ?

This look nice !

Datascript seems to be another Datalog engine (in memory only)

https://github.com/tonsky/datascript

Inspired by past work: LINQ, inline-python, crepe, DataScript, Riffle.

An in-memory database like Datascript may be worth looking into. Otherwise you could take an indexing approach: put all the data into one big map indexed by some unique key, and have a bunch of supplementary indexes that are updated on insertion.