Missing cast when comparing a guid and string columns in SAP SQL Anywhere #2075
Conversation
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
hazzik
approved these changes
Mar 20, 2019
|
Probably should be a bug on its own, not |
hazzik
changed the title
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.
Fixes #2040 for SAP SQL Anywhere.
In its case, that is not technically a regression, since that dialect has been release in 5.2.0.
(For previous (Sybase) SQL Anywhere dialects, #1856 has changed a bug for another: prior to it, converting guid to string was already failing with those dialects because they are mapping the HQL
str(meant for converting to string) to the ANSI SQLstr(meant for formatting floats).)