swaminarayan

5 ms·

61.
by swaminarayan 8mo ago
How do you evaluate whether users actually understand better, rather than just feel like they do?
62.
by swaminarayan 8mo ago
“sqlite per actor” feels like very clean actor level isolation. the part I am more curious about is how you recommend handling cross actor queries.
63.
by swaminarayan 8mo ago
most of the english language words are derive from Sanskrit. Checkout : https://en.wikipedia.org/wiki/List_of_English_words_of_Sansk...
64.
by swaminarayan 8mo ago
Nice, so it shows green/white/red badge above commentors. I would suggest HN team to integrate this feature. It looks really cool.
65.
Ask HN: Designing TTL for a B-tree KV store – feedback on dual-index approach(github.com)
4 points by swaminarayan 8mo ago|1 comments
66.
by swaminarayan 8mo ago
Adding TTL to an embedded KV store (built on SQLite's B-tree layer, not SQL). The constraint: TTL needs two conflicting access patterns – lookup by key (get expiry check) and scan by expiry time (efficient purge). Single index can&#x
67.
by swaminarayan 8mo ago
100%
68.
by swaminarayan 8mo ago
I am showing examples/ showing demo gif https://github.com/hash-anu/snkv/blob/master/demo.gif . Showing code.
69.
by swaminarayan 8mo ago
this is not vibe coded project, this is developed by understanding sqlite code. Have you ever looked into examples ? Have you checked the code ? Now my post got flagged. and If I use AI to understand code than what is wrong with that ? what
70.
by swaminarayan 8mo ago
I just looked into .c files into it, it is not using any of sqlite files. In my project I am using only sqlite layers, which are battle tested.
71.
by swaminarayan 8mo ago
I have used this https://github.com/hash-anu/sqllite-benchmark-kv/blob/main/t... , in which I called sqlite3_exec for only setting PRAGMA settings, for main operations I never used it. I have used prepare
72.
by swaminarayan 8mo ago
yes
73.
by swaminarayan 8mo ago
no dont know about it. I will check it out.
74.
by swaminarayan 8mo ago
A named key space within the same database file — keys in "users" don't collide with keys in "sessions" but both share the same WAL and transaction.
75.
by swaminarayan 8mo ago
Fair skepticism — I had the same intuition going in. The SQL layer overhead alone is probably small, you're right. The bigger gain comes from a cached read cursor. SQLite opens and closes a cursor on every operation. SNKV keeps one p
76.
Show HN: SNKV – SQLite's B-tree as a key-value store (C/C++ and Python bindings)(github.com)
36 points by swaminarayan 8mo ago|31 comments
77.
Show HN: SNKV – KV store on SQLite's B-tree with 11x less memory than RocksDB(github.com)
3 points by swaminarayan 8mo ago|0 comments