KV interface?

[glommer]

As suggested by a user on twitter today: https://twitter.com/__pragma__/status/1577756654837575680

Personally I think we should look at all the use cases where SQLite is just used for K/V queries with an ORM and ask ourselves “how could we expose a programmatic K/V API that doesn’t incur the overhead of a SQL parser and query planner?"

This seems a great idea, and great direction. But it operates on the assumption that the SQL layer is itself, expensive. My intuition is that it is, but only if prepared statements are not used. For anything that is performance sensitive, statements are likely prepared.

@psarna do you have an intuition on the cost here?

[psarna]

As per SQLite docs, "All SQL must be converted into a prepared statement before it can be run", so the model already (rightfully) forces users to prepare their statements. libSQL's prepared statement is actually a compiled program that runs on its virtual machine, and I'd expect it to be fast enough even for key/value stores, but only a benchmark would verify that.