Add better-trigram extension.

[rhashimoto]

Summary by CodeRabbit

• New Features
  • Integrated an advanced trigram extension that enhances SQLite’s capabilities.
  • Enabled automatic registration of the extension at startup for a seamless user experience.

[coderabbitai]

Walkthrough

The changes integrate a new SQLite extension, "better trigram," into the project. Modifications to the Makefile add variables, build rules for downloading/extracting the extension's source, and update compilation rules. In addition, the src/main.c file is updated to declare the external sqlite3_bettertrigram_init function and to register it automatically using SQLite’s auto-extension mechanism during runtime.

Changes

File(s)	Change Summary
Makefile	Added variables (EXTENSION_BETTER_TRIGRAM, EXTENSION_BETTER_TRIGRAM_VERSION, EXTENSION_BETTER_TRIGRAM_DIR, EXTENSION_BETTER_TRIGRAM_URL), updated the source files list and vpath, and introduced new rules for downloading, extracting, and building the better trigram extension.
src/main.c	Introduced the external declaration of sqlite3_bettertrigram_init and modified the main function to register this extension via sqlite3_auto_extension.

Sequence Diagram(s)

sequenceDiagram
    participant Main
    participant SQLite
    participant Extension
    
    Main->>SQLite: sqlite3_auto_extension(&sqlite3_bettertrigram_init)
    Note over SQLite, Extension: SQLite registers the better trigram extension
    SQLite->>Extension: Invoke sqlite3_bettertrigram_init() during connection setup
    Extension-->>SQLite: Return initialization status

Loading

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8f4a0ef and 4385485.

⛔ Files ignored due to path filters (6)

• dist/wa-sqlite-async.mjs is excluded by !**/dist/**
• dist/wa-sqlite-async.wasm is excluded by !**/dist/**, !**/*.wasm
• dist/wa-sqlite-jspi.mjs is excluded by !**/dist/**
• dist/wa-sqlite-jspi.wasm is excluded by !**/dist/**, !**/*.wasm
• dist/wa-sqlite.mjs is excluded by !**/dist/**
• dist/wa-sqlite.wasm is excluded by !**/dist/**, !**/*.wasm

📒 Files selected for processing (2)

• Makefile (5 hunks)
• src/main.c (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build (20.x)

🔇 Additional comments (7)

src/main.c (2)

5-5: Correctly declares the external function.

The external function declaration properly follows SQLite extension patterns. This will allow linking with the better-trigram extension implementation that will be built from the Makefile changes.

---

18-18: Properly registers the better-trigram extension.

The extension is correctly registered with SQLite's auto-extension mechanism, which will ensure it's loaded automatically when SQLite is initialized. The placement after sqlite3_initialize() is appropriate.

Makefile (5)

9-14: Proper setup of extension variables.

The extension variables are well-defined with appropriate naming and versioning. Using a specific tagged version (0.0.3) ensures build reproducibility, and the variable structure makes future version updates straightforward.

---

25-26: Correctly integrates extension into source files.

The better-trigram extension is properly added to the CFILES list, ensuring it will be included in the build process.

---

39-39: Appropriate path configuration for the extension.

The vpath addition correctly points to the extension directory, allowing the build system to locate the source files.

---

165-168: Well-defined download and extraction rules.

The download and extraction rules follow the pattern established for other dependencies, using secure HTTPS for downloading and properly setting up the directory structure.

---

182-188: Properly implemented compilation rules.

The compilation rules for both debug and dist builds are correctly defined, maintaining consistency with the compilation process for other components in the project.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.