tursodatabase / tursodatabase/libsql
test errors for op-sqlite + vector-search combination
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Seems like op-sqlite (starting from the release https://github.com/OP-Engineering/op-sqlite/releases/tag/10.0.0) do not properly return errors from LibSQL vector search specific statements.
For example, insert with wrong vector dimension should fail with error but instead in some configuration it just silently completes but no row is actually inserted.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the op-sqlite and LibSQL vector-search combination described in the issue, using a vector insert with the wrong dimension. Trace how errors from LibSQL vector-search-specific statements are returned through op-sqlite. Done means the invalid insert reports an error consistently and does not silently complete without inserting a row.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100