upvote

points

by Stefan-H5 hours ago |
comments
upvoteby kleton4 hours ago|
[-]
I scrolled through the entire readme and didn't see any mention of sqlite_vec. My feedback for the readme would be to optimize for signal- if it is a layer on top of sqlite_vec say what it does on top of that etc
reply
upvoteby Stefan-H3 hours ago|
parent|
next
[-]
But it is not a layer on top of sqlite_vec, so your logic seems to be: If the tool uses sqlite_vec (which it doesn't) Then it should say so in the readme. You didn't find evidence sqlite_vec in the readme, so your conclusion was that it should be added.

This is seemingly based off of your not liking the author mentioned that it would be the "sqlite of RAG" (which, notably, does not at all imply the use of sqlite, in fact, it suggests this is an alternative to sqlite).

To address your other questions about if the file format is actually a sqlite database, the readme does address that: https://github.com/christopherkarani/Wax?tab=readme-ov-file#...

The fact that the format is append-only seems to rule out that it is sqllite, but I could be wrong.

reply
upvoteby ricardobeat2 hours ago|
parent|
[-]
It uses GRDB which is an SQLite wrapper https://github.com/christopherkarani/Wax/blob/786ad6cc541392...

Nothing is very clear here.. the benchmarks might just be comparing WAL mode on vs off, or something else entirely, SQLite does not have 150ms latency on such a small database.

reply
upvoteby Stefan-H2 hours ago|
parent|
[-]
The original commenter wasn't making statements about sqlite being involved, they were saying that a specific library should be mentioned if it was involved, which it wasn't. Unless you are saying sqlite_vec is part of the dependency chain through GRDB?

It would be like commenting "If any other developers were involved in this project you should mention them."

reply
upvoteby ckarani2 hours ago|
parent|
prev|
[-]
It is Not a layer over sqlite_vec
reply