jTDS: support running JDBC tests with jTDS driver #2861
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.
Description
This PR is a part of a change originally implemented in #2320.
This change to JDBC test harness introduces the
jtds_jdbc_schedule
list file. To run the test from this new file instead ofjdbc_schedule
file it is necessary to setuseJTDSInsteadOfMSSQLJDBC
environment variable totrue
:Changes from #2860 PR are required to run jTDS tests successfully.
For
jtds_jdbc_schedule
file the intention is to use original tests unmodified where possible. Test for which modifications were required (mostly due to data types and error handling differences) are copied withjtds-
prefix.Github workfow file
jdbc-tests-with-jtds.yml
is included, but tests there are failing until #2860 is integrated. It is based onjdbc-tests-with-parallel-query.yml
workflow file.Issues Resolved
#2137
Test Scenarios Covered
The following tests from the original list are included:
sqlBatch
errorHandling
storedProcedures
transactions
Check List
By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.
Signed-off-by: Alex Kasko [email protected]