JDBC: Update to pgjdbc 42.7.7 #333
Conversation
|
Issues encountered:
|
|
Thank you very much for your evaluations. Can you converge relevant flaws into corresponding tickets to improve CrateDB? |
|
Regarding ? |
|
Hi. Because this patch seems to possibly converge well (thank you, @kneth)... and that issue has apparently been resolved (thank you, @hlcianfagna and @matriv)... is there another patch to be staged to pgjdbc/pgjdbc, about the problems around |
One option could be pgjdbc/pgjdbc#3533 , another option could be to raise a ticket in crate/crate to have |
|
Dave Cramer says: "Please make sure this does not introduce a performance regression" My question to @hlcianfagna, do you want me to try to evaluate the performance? |
Let's maybe see what the timeline would be for crate/crate#17486 instead? |
|
I have opened crate/crate#17616 as a fix to the issue with |
matriv
force-pushed
the
pgjdbc-42.7.5
branch
2 times, most recently
from
1191569 to
b6b345e
Compare
PG JDBC 42.7.5 & 6 use this function in various metadata related calls. As CrateDB doesn't support multiple catalogs, it always returns `crate` thus is registered as an alias to `current_database`. Relates: crate/crate-qa#333
PG JDBC 42.7.5 & 6 use this function in various metadata related calls. As CrateDB doesn't support multiple catalogs, it always returns `crate` thus is registered as an alias to `current_database`. Relates: crate/crate-qa#333
PG JDBC 42.7.5 & 6 use this function in various metadata related calls. As CrateDB doesn't support multiple catalogs, it always returns `crate` thus is registered as an alias to `current_database`. Relates: crate/crate-qa#333
PG JDBC 42.7.5 & 6 use this function in various metadata related calls. As CrateDB doesn't support multiple catalogs, it always returns `crate` thus is registered as an alias to `current_database`. Relates: crate/crate-qa#333
PG JDBC 42.7.5 & 6 use this function in various metadata related calls. As CrateDB doesn't support multiple catalogs, it always returns `crate` thus is registered as an alias to `current_database`. Relates: crate/crate-qa#333
PG JDBC 42.7.5 & 6 use this function in various metadata related calls. As CrateDB doesn't support multiple catalogs, it always returns `crate` thus is registered as an alias to `current_database`. Relates: crate/crate-qa#333
PG JDBC 42.7.5 & 6 use this function in various metadata related calls. As CrateDB doesn't support multiple catalogs, it always returns `crate` thus is registered as an alias to `current_database`. Relates: crate/crate-qa#333
PG JDBC 42.7.5 & 6 use this function in various metadata related calls. As CrateDB doesn't support multiple catalogs, it always returns `crate` thus is registered as an alias to `current_database`. Relates: crate/crate-qa#333
PG JDBC 42.7.5 & 6 use this function in various metadata related calls. As CrateDB doesn't support multiple catalogs, it always returns `crate` thus is registered as an alias to `current_database`. Relates: crate/crate-qa#333
|
retest this please |
|
retest this please |
Use `null` instead of empty string `''` to avoid adding `like` WHERE clauses to the metadata queries.
|
retest this please |
1 similar comment
|
retest this please |
About
pgjdbc 42.7.5 has been released yesterday. When running the stock jdbc test cases, errors can be observed on Jenkins after bumping manually per this PR.
References
Validating an automatic Dependabot update failed over here on GHA, apparently tripping test_getFunctions, test_getColumns, test_getPrimaryKeys, and test_getTables in
JdbcMetaDataTest.java./cc @kneth, @seut