Conversation
Collaborator
Author
|
Matching SQL Server implementation: TabularisDB/tabularis-sqlserver-plugin#31 (stacked on the pagination fix in #30 of that repository). The new flag must be registered in the Tabularium driver-kind schema before publishing the plugin; registry code and production configuration remain untouched. |
This branch has not been deployed
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.
Summary
Backward compatibility
Validation
Coordination
Refs TabularisDB/tabularis-sqlserver-plugin#26.
Plugin pagination fix: TabularisDB/tabularis-sqlserver-plugin#30.
The matching plugin implementation is on feat/table-query-templates; this draft freezes the additive contract for joint review.
Tabularium
Before publishing the plugin, register the optional boolean table_query_templates (default false) under the driver-kind capabilities schema. Ingestion uses lenient AJV validation with removeAdditional: all, which otherwise strips the flag. No database migration, endpoint or SDK change is needed. Registry production configuration has not been modified.