Fix Load Tests Due to Multiple ResultSets
#1073
Merged
+2
−1
Conversation
This file contains 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
|
somesylvie
approved these changes
May 8, 2024
jcrichlake
approved these changes
May 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix Load Tests Due to Multiple
ResultSetsThe load tests started failing (and perhaps outside load tests too) due to multiple
ResultSets being returned when getting linked message IDs.This is due to multiple SQL statements (separated by
;) in the SQL string. So, even though that second SQL statement was just a SQL comment (notice the--), the API throws an exception because it wants to return multipleResultSets when we are using an API that only allows oneResultSet.Issue
#1044.