You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VeloxUserError: Cannot cast REAL '2.0523335847491578E23' to BIGINT. Loss of precision during arithmetic conversion: (long) 2.0523335847491578E23 cast((field_0) as BIGINT)
See reference from the spec below (see 6.13, cast specification). Postgres also throws. To me, this seems like a bug.
If TD is approximate numeric, then
Case:
a) If SD is numeric, then
Case:
i) If there is a representation of SV in the data type TD that does not lose any leading significant digits after rounding or truncating if necessary, then TV is that representation. The choice of whether to round or truncate is implementation-defined.
ii) Otherwise, an exception condition is raised: data exception — numeric value out of range.
Prestissimo throws:
CC: @rschlussel @spershin @tdcmeehan @aditi-pandit @kgpai @kagamiori @gggrace14 @amitkdutta
The text was updated successfully, but these errors were encountered: