A quick clarification since the title mentions SQLite:
This is not just a thin wrapper over SQLite.
The goal was to build a *minimal KV interface* (put/get/delete) that feels like a hashmap, while delegating durability + ACID guarantees to SQLite underneath.
So you don’t deal with:
* SQL
* schema design
* connection management
Just a simple embedded KV store in a single header.
Also happy to explain design decisions or internals if anyone’s curious
A quick clarification since the title mentions SQLite:
This is not just a thin wrapper over SQLite.
The goal was to build a *minimal KV interface* (put/get/delete) that feels like a hashmap, while delegating durability + ACID guarantees to SQLite underneath.
So you don’t deal with:
* SQL * schema design * connection management
Just a simple embedded KV store in a single header.
Also happy to explain design decisions or internals if anyone’s curious