You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use case
In our application we got sporadically a PRIMARY KEY violation, which we could not explain. After investigating we found out, that this happens since we updated to 6.2.0 (6.1.7.jre8-preview works)
Steps to reproduce
do several pstmt.setNull & pstmt.setString commands ln a certain order
@rPraml,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects. Thanks,
Microsoft Pull Request Bot
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Use case
In our application we got sporadically a PRIMARY KEY violation, which we could not explain. After investigating we found out, that this happens since we updated to 6.2.0 (6.1.7.jre8-preview works)
Steps to reproduce
do several pstmt.setNull & pstmt.setString commands ln a certain order
How to fix