【Bug?】The behavior of the UPDATE statement using the CASE clause is wrong #313
Replies: 2 comments
-
Thanks for the details. Yes, I can confirm this is a bug, I'll try to get this fixed ASAP. In the meantime you can get the correct results either by reversing the order of the UPDATE r
SET r.crf3c_integer_column = (
CASE
WHEN r.crf3c_integer_column IS NOT NULL
THEN r.crf3c_integer_column + 1
ELSE NULL
END
)
FROM crf3c_rank0_3 AS r
WHERE r.crf3c_rank0_3id IS NOT NULL; or by removing it entirely ( UPDATE r
SET r.crf3c_integer_column = r.crf3c_integer_column + 1
FROM crf3c_rank0_3 AS r
WHERE r.crf3c_rank0_3id IS NOT NULL; I've moved this to issue #314 to track it until it's resolved. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you for your prompt reply. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have the following data:
After executing the following UPDATE, all the values in the [crf3c_integer_column] column are NULL.
Isn't this a bug?
The result is below:
Thanks in advance for your support.
Beta Was this translation helpful? Give feedback.
All reactions