Alexander Polyankin comments

Results 183 comments of


                                            Alexander Polyankin

Date range filter does not respect date format settings

please confirm with the product before merging the fix

Field visibility setting does not affect queries explicitly including that field

The bug can be still reproduced on `9a96a65abf8ead0364bc7dc356b0b5baf951b27c`. It's unclear what the fix should be - just hiding columns on the FE like we do with "Only in detail views"...

Field visibility setting does not affect queries explicitly including that field

I'm pretty certain that we should not silently drop this field from queries

Internal remapping triggers externally remapped columns to appear via models

Can repro in v57, not v56

Autocompletion of JSON fields in the native editor inserts wrong character

Removed `.Frontend` since there is nothing we can do right now until the API is fixed, similar to this https://github.com/metabase/metabase/issues/26218#issuecomment-1895471586

Caching a model with columns with repeated names will generate invalid queries

Already fixed in v57

Metrics with a joined column as a default time dimension fail with invalid query error

https://metaboat.slack.com/archives/C0645JP1W81/p1759757499305489?thread_ts=1759671628.791759&cid=C0645JP1W81

Metrics with a joined column as a default time dimension fail with invalid query error

This is quite problematic. To make it work, we would need to include all relevant joins and custom expressions from the metric definition when creating a query in `(lib/query …)`....

Setting column Visibility to "Only in detail views" stills shows the column as being included in Notebook

I don't think that we should hide this column in the notebook editor.

Setting column Visibility to "Only in detail views" stills shows the column as being included in Notebook

Pretty certain that's it's about viz mainly, so "Only in detail views" should not remove it from the QB. To confirm and close