tursodatabase / tursodatabase/libsql
Document dynamically loaded extension compatibility
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
libSQL already diverged in the extension management - the extension API structure contains additional fields related to virtual WAL, not present in SQLite. Because of that, compiling an extension with libSQL header and running it on SQLite, or vice versa, is not defined behavior. We should document that we highly recommend (and actually just require) dynamically loaded extensions to be recompiled with a libSQL header if they are to be used with libSQL.
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
No documentation file or test is named. Start by locating the repository documentation covering extension management and dynamically loaded extensions, then document the libSQL/SQLite header compatibility requirement and the need to recompile extensions with a libSQL header; done means the recommendation is clearly recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100