tursodatabase / tursodatabase/libsql
ext/crr: port to a breaking API change after merging with SQLite 3.44.0
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Ref: https://github.com/tursodatabase/libsql/pull/625
We unfortunately introduced a breaking API change in sqlite3_module + sqlite3_create_module API for virtual tables. crr extension is one of our in-source victims, because it relies on the xPreparedSql call that's libSQL-specific. It needs to be ported from sqlite3_create_module to libsql_create_module API.
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
Start by inspecting the ext/crr extension and the API change described in the referenced pull request. Port its virtual-table module creation from sqlite3_create_module to libsql_create_module, then verify that the extension builds successfully with the updated API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100