Expose type modifier in Column struct #1145
Merged
Conversation
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
|
+1 for this PR. This would enable the result set handling in a much better way rather than falling back to defaults. In fact, rather than type modifier, we should expose the derived precision & scale at the upper level API like Statement. |
Contributor
Author
|
@paolobarbolini how does this PR look? |
Contributor
Author
|
This PR closes #1300 |
paolobarbolini
added a commit
that referenced
this pull request
Dec 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
Expose the 4-byte type-specific type modifier on the Column struct
Why
I would like access type modifiers for prepared statement columns. E.g. for a numeric column I would like to get the numeric precision and scale. For a varchar column I would like to get the varchar length limit.
Context
This is an extension of #1084 where other table and column OIDs were exposed in Column, and exposing type modifiers was noted as a possibility.