It looks like the MAX function truncates large lon...
# troubleshooting
t
It looks like the MAX function truncates large longs and loses precision. For example,
select MAX(1639054811930692679) from table
returns
1.63905481193069261E18
. Is this behavior expected?
j
currently it is. all of these scalar aggregation functions cast to double. i’ll let someone else chime in on what the plan is for the future here, though
t
Would it make sense to keep the original type instead?
k
it does. please file an issue also add it to https://poll.ly/#/Pvy1rpp2/P0KwomM2
t