tursodatabase / tursodatabase/libsql
User-defined functions: consider keeping state in WebAssembly instances
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
One of the applications of user-defined functions are user-defined aggregates, which are actually built on top of UDFs - https://www.sqlite.org/appfunc.html#the_aggregate_function_callbacks . It would be a very nice boost to keep the intermediate state of computations within the Wasm instances used to run the step function, without having to store it externally and without recreating the instance on each call
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
The issue names no file or test; begin with the SQLite aggregate callback documentation and trace the Wasm instance used by the UDF step function. Before implementation, define how intermediate aggregate state remains in that instance across calls and how completion can be verified without external storage or recreating the instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite, wasm
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100