Three ways a panel can say nothing, and why they differ
Two panels refuse with their reason, one stays empty in the engine's own words, a third reads not measured, and each of those is a different claim about the database.
4 posts
Writing on LibreDB
The embedded ordered key-value store — a file, no server and no wire protocol. Mapped onto the interface by convention rather than by emulating SQL. Where it stops: No sessions and no index objects exist, so those two panels are absent with their reason rather than answered empty. Maintenance operations are refused, not faked.
Five verbs over an ordered keyspace, with a catalog on top
The whole grammar is get, put, delete, prefix and range, and yet the tree still shows declared columns for the namespaces that have them.
Opening a LibreDB file takes an exclusive lock
There is no host, no port and no server, and the lock sidecar means command-line tooling cannot hold the same file while a connection is open.
What a plan-mode model is told about a LibreDB file
The grounding read is bounded by the provider itself, and the plan rules say outright that the rows are groupings derived from one scan.