test: Fix failing testSqrtFunction test for SQLite #1806
Closed
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
This test fails locally for me, but not on TeamCity for some reason. According to SQLite documentation, using the SQRT math function on a negative value returns NULL, but there is no mention of an error being thrown, so we need not expect an exception. I tried it on DataGrip and using exec function to execute raw SQL in the test, and both did not throw an error and simply returned null.
|
Closing this as it's resolved in #1853 |
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.
This test fails locally for me, but not on TeamCity for some reason. According to SQLite documentation, using the
SQRTmath function on a negative value returns NULL, but there is no mention of an error being thrown, so we need not expect an exception. I tried it on DataGrip and using exec function to execute raw SQL in the test, and both did not throw an error and simply returned null.