Mateusz "Serafin" Gajewski

@martint this is unfortunate if you want to use this new syntax to produce a JSON like: ``` trino> select row(orderkey as orderkey, partkey as partkey, {'returnflag': returnflag} as flag)::json...

@martint ``` trino> select row(orderkey as "orderkey", partkey as "key", {'returnflag': returnflag} as "flag")::json from tpch.sf1.lineitem limit 10; _col0 ------------------------------------------------------------- {"orderkey":2400001,"key":132304,"flag":{"returnflag":"N"}} {"orderkey":2400001,"key":24513,"flag":{"returnflag":"R"}} {"orderkey":2400001,"key":175232,"flag":{"returnflag":"N"}} {"orderkey":2400001,"key":119658,"flag":{"returnflag":"A"}} {"orderkey":2400001,"key":89532,"flag":{"returnflag":"A"}} {"orderkey":2400002,"key":188783,"flag":{"returnflag":"R"}} {"orderkey":2400002,"key":67505,"flag":{"returnflag":"R"}} {"orderkey":2400002,"key":142916,"flag":{"returnflag":"R"}} {"orderkey":2400002,"key":182905,"flag":{"returnflag":"A"}} {"orderkey":2400002,"key":80484,"flag":{"returnflag":"R"}}...

``` trino> select row(orderkey as "orderkey", partkey as "key", {'returnflag': returnflag} as 'flag')::json from tpch.sf1.lineitem limit 10; Query 20250313_170521_00047_angdu failed: line 1:84: mismatched input ''flag''. Expecting: select row(orderkey as "orderkey",...

@raphw great! This will allow us to move forward with testing EA builds :) Appreciate the quick turnaround!

@sajjoseph VTs are not suitable for that case at the moment

Nice :)

@dysn that's correct, I think that this is a viable option to support Arrow Flight on top of the spooled protocol.

What about syntax `11 AS BIGINT` or `11 AS TYPE BIGINT` ?

@martint do we have a way forward for this change? I agree with what David said about ambiguity and casts. This syntax makes a lot of sense from usability perspective

@umartin please open a PR and we will review it