We support extension loading in the library, but need a mechanism in the server to also allow that.
Contributor guide
Tech stack
csql
Domain
backenddatabase
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
C programmingSQLite extension APIlibSQL internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the existing extension loading in the libSQL library (likely in src/extension.c or similar). Understand how the server component (e.g., in src/server/) is structured. Look for any existing hooks or configuration for loading plugins. The server will need a configuration option (e.g., command line flag or config file) to specify extension paths and a mechanism to load them at startup. Check the library's extension loading code to reuse or adapt it. Also review any tests for extension loading in the test suite.
