-
Notifications
You must be signed in to change notification settings - Fork 853
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Numeric precision should not be 131089 #2188
Comments
davecramer
added a commit
to davecramer/pgjdbc
that referenced
this issue
Jun 23, 2021
…specified fixes: Issue pgjdbc#2188
davecramer
added a commit
to davecramer/pgjdbc
that referenced
this issue
Jul 2, 2021
closed by #2189 |
judahrand
added a commit
to judahrand/debezium
that referenced
this issue
Oct 5, 2021
This puts the method in line with pgjdbc/pgjdbc#2188 where expected value was changed from `131089` to `0`. However, for numeric arrays the issue remains and so `131089` remains the correct value for them.
gunnarmorling
pushed a commit
to debezium/debezium
that referenced
this issue
Oct 8, 2021
This puts the method in line with pgjdbc/pgjdbc#2188 where expected value was changed from `131089` to `0`. However, for numeric arrays the issue remains and so `131089` remains the correct value for them.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the case where numeric precision is not specified in the type ie numeric(8,2) we are currently returning the display size which is certainly incorrect.
pgjdbc/pgjdbc/src/main/java/org/postgresql/jdbc/PgDatabaseMetaData.java
Line 1650 in 7aea513
I'm inclined to fix this and backpatch it as it is a bug, however I'm a little concerned at breaking something. OTOH, it's clearly wrong.
The text was updated successfully, but these errors were encountered: