Document driver-based schema context for AI Query Assist#11
Open
debba wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (3 files)
Reviewed by kimi-k2.6 · Input: 34K · Output: 2.5K · Cached: 114.7K |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
The AI Assistant guide now explains how schema context is loaded for the current connection and schema, what metadata is included, and why generation waits for that context before sending a request.
The plugin documentation covers both compatibility paths: existing drivers continue to work through the standard metadata methods, while drivers that can fetch metadata more efficiently may implement the optional get_ai_schema_context JSON-RPC method. The building guide also points plugin authors to this behavior at the stage where table and column metadata become available.
This documents the behavior introduced in TabularisDB/tabularis#479 for TabularisDB/tabularis#477.
Validation