Closed iaroslaff closed 9 months ago
Probably this is because of how range is special-cased in relgen
.
If we can fix it by using a simple_special_case
instead so it works in singleton mode, that's probably best?
Either way, we should produce a real error from somewhere when we need to compile a function call in singleton mode and it is marked func_sql_expr
and we don't have a specialization
Steps to Reproduce:
edgedb migration create -I<you_edgedb_instance>
;edgedb migrate -I<you_edgedb_instance>
Gives an error:
Schema:
But if you replace range(...) with simple string for experimentation - migration is created and applied perfectly well:
constraint expression on ( contains("abc", __subject__) );