Hello,

I am getting inconsistent representation of long types.

1661817599972 is the unix timestamp in milliseconds for Monday, August 29, 2022 11:59:59.972 PM GMT

when I execute:

`select 1661817599972 as t`

the result is:

166181759997 (last digit truncated)

The number is correctly cast as a bigint according to `describe select 1661817599972 as t`.

However when I execute:

select timestamp_millis(1661817599972) as t

the result is (correctly) `2022-08-29T23:59:59.972+0000`. So the internal representation of the object seems correct. This appears to happen for bigints only. For instance:

`select 16618175678 as t`

yields:

1661817567

but

`select 1661817567 as t`

also yields

1661817567

DBR 11.2

Thank you,

Cosimo.

PS: displays correctly in DBSQL