Remove stock JDBC client tests

[mfussenegger]

The integration tests in the crate repo already use the stock PostgreSQL
JDBC client.

[matriv]

I'd say to not remove those, as very recently helped us identify an issue: crate/crate#14754. What do you think?

[amotl]

Hi.

We converged that code into the cratedb-examples repository the other day, so I think it will be good to remove it here.

• QA: Add Java JDBC test cases cratedb-examples#113

I'd say to not remove those, as very recently helped us identify an issue.

I agree. There might just be a new issue upcoming, which has been caught when upgrading org.postgresql:postgresql from 42.6.0 to 42.7.0.

• Bump org.postgresql:postgresql from 42.6.0 to 42.7.0 in /by-language/java-qa cratedb-examples#162

With kind regards,
Andreas.

[matriv]

Apologies, but I don't agree to remove the tests from here, crate-qa CI is something that we monitor closely and indicates possible issues when we change things in CrateDB. Whereas cratedb-examples has a completely different purpose, it's to show basic usage of various integrations and it's not connected to CrateDB dev lifecycle.

[amotl]

All right. So, let's close this PR and maybe let's also add some Dependabot configurations to the QA tests here, so that errors like currently happening at GH-288 can be caught earlier in the future?

Do you have any strong objections, @mfussenegger?

[matriv]

Do you have any strong objections, @mfussenegger?

Yep, let's here other's opinion on this one before closing, thx!

[mfussenegger]

The idea would've been to extend the tests in crate/crate to fill in any gaps.
Having more tests is good, having redundant test cases not so much.

But probably makes sense to keep it here, given that JdbcMetaDataTest is very client specific.

[matriv]

Totally agree to try to move the stuff that makes sense to crate/crate repo and here only have smoke tests if necessary.