br1ghtyang / asterixdb

Automatically exported from code.google.com/p/asterixdb
0 stars 0 forks source link

Integer types are not implicitly widened #578

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
See the following example and the comments inlined:

drop dataverse foo if exists;
create dataverse foo;
use dataverse foo;

create type footype as open {
id: int64
};

create dataset foo(footype) primary key id;

// This does not work since there is a type mismatch: int32 != int64
insert into dataset foo({"id": int32("1")});

What should happen is that the id should be implicitly casted (since it's a 
widening cast) into int64.

Original issue reported on code.google.com by zheilb...@gmail.com on 24 Jul 2013 at 11:47

GoogleCodeExporter commented 8 years ago

Original comment by zheilb...@gmail.com on 4 Oct 2013 at 10:15