a double value can be set to a int32/int64 property successfully

[Nicole00]

My tag has a property with data type int32, when I insert a double value, the expect result is failure, but the result is succeed.

And the query value is forced changed to int32, which is wrong.

[jievince]

• Mysql, oracle, tidb, sql server, postgresql allow implicitly convert float to int;

tidb:

my:[email protected]:4000=> create table test.test (a int);
CREATE TABLE
my:[email protected]:4000=> insert into test.test values (18.34);
INSERT 1
my:[email protected]:4000=> select * from test.test;
 a
----
 18
(1 row)

SQL server:

[jievince]

• CockroachDB will report an error:

root@:26257/defaultdb> create table test(a int);
CREATE TABLE

Time: 6ms total (execution 6ms / network 0ms)

root@:26257/defaultdb> insert into test values (18.34);
ERROR: value type decimal doesn't match type int of column "a"
SQLSTATE: 42804
HINT: you will need to rewrite or cast the expression

[jievince]

• GQL says nothing about it.
  

[Nicole00]

When insert value 1.6 into nebula int32 property, the query result is 1.

When insert value 1.6 into mysql int32 property, the query result is 2, which is rounding.

Should we keep the same behavior with other dbs ?

[jievince]

When insert value 1.6 into nebula int32 property, the query result is 1.

When insert value 1.6 into mysql int32 property, the query result is 2, which is rounding.

Should we keep the same behavior with other dbs ?

Good catch. They will round the float.