Return precision values for non-decimal columns#367
Merged
staticlibs merged 1 commit intoduckdb:mainfrom Sep 12, 2025
Merged
Conversation
This PR makes `ResultSetMetaData#getPrecision()` to return non-zero values for integral numbers, floating point, date/time and string columns. Unlike the `DECIMAL` type, where actual column precision is returned, for other types this call is expected to give a hint to a client software how much space the textual representation of the field is going to take. Previously returned 0 value appeared to cause problems in some of such clients. Values returned are consistent with ones returned by Postgres. Testing: new test added for all types. Fixes: duckdb#340
staticlibs
added a commit
to staticlibs/duckdb-java
that referenced
this pull request
Sep 15, 2025
This is a backport of the PR duckdb#367 to `v1.4-andium` stable branch. This PR makes `ResultSetMetaData#getPrecision()` to return non-zero values for integral numbers, floating point, date/time and string columns. Unlike the `DECIMAL` type, where actual column precision is returned, for other types this call is expected to give a hint to a client software how much space the textual representation of the field is going to take. Previously returned 0 value appeared to cause problems in some of such clients. Values returned are consistent with ones returned by Postgres. Testing: new test added for all types. Fixes: duckdb#340
staticlibs
added a commit
that referenced
this pull request
Sep 15, 2025
This is a backport of the PR #367 to `v1.4-andium` stable branch. This PR makes `ResultSetMetaData#getPrecision()` to return non-zero values for integral numbers, floating point, date/time and string columns. Unlike the `DECIMAL` type, where actual column precision is returned, for other types this call is expected to give a hint to a client software how much space the textual representation of the field is going to take. Previously returned 0 value appeared to cause problems in some of such clients. Values returned are consistent with ones returned by Postgres. Testing: new test added for all types. Fixes: #340
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
1 participant
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.
This PR makes
ResultSetMetaData#getPrecision()to return non-zero values for integral numbers, floating point, date/time and string columns.Unlike the
DECIMALtype, where actual column precision is returned, for other types this call is expected to give a hint to a client software how much space the textual representation of the field is going to take. Previously returned 0 value appeared to cause problems in some of such clients.Values returned are consistent with ones returned by Postgres.
Testing: new test added for all types.
Fixes: #340