Replies: 1 comment
|
Maybe it is due to the real value not having any implied precision, so it is converting to maximum precision, and you are seeing the floating-point representation. You should probably specify decimal data as decimal values. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
KQL query below
will generate a table containing these rows
Is this by design? If so, is it documented anywhere? I'm sure it can feel unexpected to some.
All reactions