Describe the bug

create table t (v1 int, v2 int, v3 int);
explain insert into t (v3, v2, v1) values (1, 2, 3); 
                       QUERY PLAN                        
 BatchExchange { order: [], dist: Single }
 └─BatchInsert { table: t }
   └─BatchValues { rows: [[1:Int32, 2:Int32, 3:Int32]] }

Expected behavior

Should this not be BatchValues { rows: [[3:Int32, 2:Int32, 1:Int32]] }? I am aware that the values are still defined in the order 1, 2, 3, but as a user I would not expect this behaviour.

Additional context

Relates to Please only work on this after PR is merged:


closed by

© 2022 - All rights reserved.