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 Pull Request closes goccy/bigquery-emulator#217
I added a unary minus operator because it was not implemented before.
As tested here, It seems to work fine with number literals, but using
-
on columns causes an error as described in the linked issue.In this PR, I implemented the unary minus operator. It is basically the same as the SAFE_NEGATE function, as shown in the link below. What different is, an exception occurs when there's an overflow.
https://cloud.google.com/bigquery/docs/reference/standard-sql/mathematical_functions#safe_negate
out of scope
This unary minus operator implementation uses
SAFE_NEGATE
inside, but do not changeSAFE_NEGATE
behaviour. Currently,SAFE_NEGATE
has some incompatibilities. For example,NaN
,NaN
is expected but it returnsnil