-
Notifications
You must be signed in to change notification settings - Fork 556
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
Fix wrong precision #808
Fix wrong precision #808
Conversation
A related issue(trinodb/trino#10541) |
|
The second commit describes:
Why? The original implementation maps |
|
Thanks @tangjiangling for the pull request :) I don't mind to create another patch release, but I'll need to run integration test against trino to see if there's more issues. In the mean time, before merging the PR, would you mind to sign CLA and rebase? I changed merge target from master to develop, and I'll add some more tests. |
signed. What does rebase mean? Is it a combination of all the "Merge pull request ClickHouse#..." into a single commit? |
Sorry, I forgot to set the email, I will do that soon. |
f8cd9e4
to
e916539
Compare
done. |
|
Yes, squash may work too.
I think we should consider both cases. When the column is numeric, we use
I'll need to look into this tonight and add some more tests accordingly. Update: I'll fix the these issues and release |
+1, I will update the current PR later this evening. |
e916539
to
ab51406
Compare
I fixed it on the basis of this #815 . |
|
ab51406
to
a564b7b
Compare
|
a564b7b
to
22a36ca
Compare
22a36ca
to
6ee8885
Compare
|
|
Fixed by #815. Now we can close this. |
Fixes: #807
com.clickhouse.jdbc.ClickHouseDatabaseMetaData#getColumns
returns the wrong precision, which is against the JDBC standard.