MATCH queries *silently* fail
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
I am trying to do a full-text search using FTS4, but for some reason my queries with MATCH keyword fails. I have tried both asm and wasm versions with debug and production builds but the result is the same.
The worst is that sql.js does not indicate errors by any means! You can try it on the official demo too: modify the command such that it must fail, and observe how nothing is reported.
So my questions are:
- Why do
MATCHqueries fail? - Are you aware that error reporting is completely broken (on browser)?
It might be wise to write some tests to ensure this won't happen again. I'll be happy to contribute if you are interested too.
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
Reproduce the FTS4 MATCH failure in the official demo using both asm and wasm builds, then trace why the browser reports no error. Add regression coverage for the failing query and error reporting; done means the failure is diagnosable rather than silent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, sqlite, wasm
- Domain
- databases, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100