I’m seeing some unexpected behaviour around BIGINTs. [I’m running MapD v3.2.2 on Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-1030-aws x86_64).]
If I create a table as follows:
CREATE TABLE some_ints( intval BIGINT );
then insert a row as follows:
INSERT INTO some_ints VALUES(4489949424181064562);
if I then select the contents of that table I get a single row with the value being 4489949424181064700.
As far as I’m aware the value inserted should be well inside the max range of BIGINT. I’m assuming that BIGINT will be inline with Calcite in the range -9223372036854775808 to 9223372036854775807.
Is there something I’m missing?
I also see the same behaviour if I stream insert the data.