We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Any
CREATE TABLE test (c1 varchar(1), c2 varchar(3))
Columns mixing up on batch insert and leads to invalid data
The same result expected like if no batch of inserts
Reproducible with the com.microsoft.sqlserver.jdbc.preparedStatement.BatchExecutionWithBulkCopyTest.testReverseColumnOrder() unit test from the PR
com.microsoft.sqlserver.jdbc.preparedStatement.BatchExecutionWithBulkCopyTest.testReverseColumnOrder()
Possible fix: PR
The text was updated successfully, but these errors were encountered:
We'll take a look and get back to you, but our response will be a bit delayed as were in the middle of finalizing a couple of hotfix releases.
Sorry, something went wrong.
Resolved by #1992
No branches or pull requests
Driver version
Any
SQL Server version
Any
Client Operating System
Any
JAVA/JVM version
Any
Table schema
CREATE TABLE test (c1 varchar(1), c2 varchar(3))
Problem description
Columns mixing up on batch insert and leads to invalid data
Expected behavior
The same result expected like if no batch of inserts
Actual behavior
Reproducible with the
com.microsoft.sqlserver.jdbc.preparedStatement.BatchExecutionWithBulkCopyTest.testReverseColumnOrder()
unit test from the PR
Error message/stack trace
Reproducible with the
com.microsoft.sqlserver.jdbc.preparedStatement.BatchExecutionWithBulkCopyTest.testReverseColumnOrder()
unit test from the PR
Any other details that can be helpful
Possible fix: PR
JDBC trace logs
Reproducible with the
com.microsoft.sqlserver.jdbc.preparedStatement.BatchExecutionWithBulkCopyTest.testReverseColumnOrder()
unit test from the PR
The text was updated successfully, but these errors were encountered: