Fix DatabaseMetaData.getColumns nullability inconsistency #15214
Conversation
This file contains 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
Make it easier to map values to columns.
`DatabaseMetaData.getColumns` reports nullability in two result columns
- NULLABLE, a number (0, 1, 2)
- IS_NULLABLE, a varchar column ("YES", "NO", "")
This fixes the `TrinoDatabaseMetaData` so that information returned in
those two ways is consistent.
findepi
force-pushed
the
findepi/jdbc-enh
branch
from
abddbde
to
fc9d43e
Compare
losipiuk
approved these changes
Nov 28, 2022
ebyhr
approved these changes
Nov 28, 2022
Closed
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.
DatabaseMetaData.getColumnsreports nullability in two result columnsThis fixes the
TrinoDatabaseMetaDataso that information returned inthose two ways is consistent.