-
Notifications
You must be signed in to change notification settings - Fork 19
Initial JDBC support #99
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
Conversation
b4e37f9
to
1e0d349
Compare
Cleanup the directory once before all tests: move it from the TarantoolControl constructor to the static block.
It fixes race conditions in testLongParallelCloseReconnects: an attempt to start jdk-testing instance against already started one could be performed because stopTarantool() did not wait until an instance will really stop. Use these functions in setupEnv() / cleanupEnv() to avoid possible race conditions.
Updated constants to be in sync with tarantool IPROTO. Added integration tests for the working JDBC functionality. Fixed travis script to use tarantool 2.0 which is required for SQL. Fixed failing user permission calls in tarantool initialization script. Closes #39 ---- Rebase fixes (Alexander Turenko): * Start tarantool from the Java code in JDBC tests (use TarantoolControl).
Fixed several mistakes in get primary keys metadata API. Corrected type mismatch when parsing server response. Added sorting of result rows by column name. Fixed order of columns in result set. Wrapped errors into SQLException. Improved test coverage. Closes #41 ---- Rebase fixes (Alexander Turenko): * Start / stop jdk-testing instance using TarantoolControl in JdbcExceptionHandlingTest.
Fixed exception when packing date/time parameters of prepared statement. Added test for parameter binding methods. Closes #43
Added connection property `socketTimeout` to allow user control over network timeout before actual connection is returned by the driver. This is only done for default socket provider. The default timeout is left to be infinite. Implemented `Connection.setNetworkTimeout` API to make it possible to change the maximum amount of time to wait for server replies after the connection is established. The connection that has timed out is forced to close. New subsequent operations requested on such connection must fail right away. The corresponding checks are embedded into relevant APIs. Closes #38
1e0d349
to
a83801f
Compare
Removed implicit test directory cleanup between tests: 292671e. Fixed flaky CI fails on testLongParallelCloseReconnects: a588557. Used TarantoolControl in the JDBC tests (see changed commit messages). @dgreenru Says he cannot see the PR for now, but blindly okay with the merge. @ztarvos I’m waiting for your comments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Totktonada, I have just one comment regarding the changes in JdbcExceptionHandlingTest.java.
Otherwise, LGTM. Thank you.
src/test/java/org/tarantool/jdbc/JdbcExceptionHandlingTest.java
Outdated
Show resolved
Hide resolved
It is needed to get rid of having tarantool connection in the unit test.
No description provided.