Ontologically invalid queries should not be allowed. See example. about typeql HOT 7 CLOSED

This comment was originally posted by @haikalpribadi on 2017-04-24 13:33:48+02:00.

cc: Sheldon Hall
this might be relevant to the the "type inference upon query planning" thing that Sheldon was working on.

from typeql.

This comment was originally posted by Filipe Peliz Pinto Teixeira on 2017-11-02 12:21:19+01:00.

Felix Chapman this is done no?

from typeql.

This comment was originally posted by Felix Chapman on 2017-11-02 12:23:02+01:00.

Filipe Peliz Pinto Teixeira It depends what it means. In general we allow invalid queries, but we do check super-simple stuff like "is the type there". For example, Graql won't mind if you say match $r ($x, $y); $r isa person; $r isa dog; or whatever.

from typeql.

This comment was originally posted by Filipe Peliz Pinto Teixeira on 2017-11-02 12:24:28+01:00.

Felix Chapman I suppose then the goal of this task is to optimise around not executing queries which we know are invalid. Like the above having two types. So this is not done then I would say.

from typeql.

This comment was originally posted by @kasper-piskorski on 2018-04-13 11:05:10+02:00.

isn't that a feature?

from typeql.

This comment was originally posted by Jason Liu on 2018-04-13 13:23:35+02:00.

@kasper-piskorski I think this should be allowed

from typeql.

Generally, detecting invalid queries in the schema is now caught by type inference before the query is executed in TypeDB as of 2.x

from typeql.