[JAVA] JDBC note update. #6418
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
4 Skipped Deployments
|
dhtclk
approved these changes
Jun 18, 2026
|
Docs PR opened: ClickHouse/mintlify-docs-dev#228 Added a JDBC V2 note explaining that getTypeInfo now returns null for LITERAL_PREFIX and LITERAL_SUFFIX on numeric types. |
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
Adds note to JDBC doc about differences in type info between v1 and v2
Checklist
Note
Low Risk
Documentation-only change to the JDBC integration guide; no runtime or API code is modified.
Overview
The JDBC migration guide’s Database Metadata Changes section now documents a V1 vs V2 difference for
DatabaseMetaData.getTypeInfo(): in V2,LITERAL_PREFIXandLITERAL_SUFFIXarenullfor types that should not use literal quoting (e.g. numeric types), whereas V1 returned non-null values. The note clarifies that tools generating SQL should rely on these columns when quoting literals by type.Reviewed by Cursor Bugbot for commit 3b45464. Bugbot is set up for automated code reviews on this repo. Configure here.