Alexander Polyankin
Alexander Polyankin
With the current UI, it's actually better not to disable it to support queries with many parameters. This is not ideal.
yes model column reordering is not implemented yet. It should be done on the metadata level, not viz setting.
It's not clear without in-depth understanding of all fingerprinting cases and DBs whether this can be harmful or not.
we should not create queries with invalid bucketing
Viz issue - remapped data is returned
Still not fixed
Issue with sample data. Should be fixed there (is it serialized?). No QP bug here. Just remove binning from the column
This part is interesting `"ERROR: column source. Table Name - Column__name_ef701e16 does not exist Position: 249"` I guess the table name + column name exceeds the DB limit for identifiers
Repro, for PG: ``` create table test( id int, fk int, big_column_big_column_big_column_big_column_big_column_big_column_big_column_big_column_big_column_big_column_big_column_big_column_big_column_ varchar ); create table test_2( id int, big_column_big_column_big_column_big_column_big_column_big_column_big_column_big_column_big_column_big_column_big_column_big_column_big_column_ varchar ); ``` * Add the db, sync * Table...
For some reason I couldn't break it easily with normal joins