losfair / losfair/mvsqlite

Change notification for queries

Open
#21 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Rust
Stars
1.6k
Forks
48
PR merge metrics
No merged PRs in 30d

Description

The current primitives provided by mvstore/mvsqlite is enough to implement efficient change notification for queries: notify the app when the result of running a query may change.

The mechanisms involved are `read_set` and the `interval` field provided by the `/stat` endpoint. Pages read by a transaction can be recorded, and later checked against `/stat` response.

However, exposing this would either need modification to SQLite itself, or the use of thread-local state.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading how mvstore/mvsqlite exposes transaction read_set data and the /stat endpoint's interval field. The work is complete when the application can be notified that a query result may have changed, but the payload does not identify specific files, tests, or an implementation boundary.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, sqlite
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.