Filters & use of table aliases

EvaS · March 16, 2018, 6:54am

Hi,
this is a known issue, you can´t use aliases when you use certain filters:

Field filter fails if it references a column from an aliased table

opened 05:19PM - 07 Sep 16 UTC

Type:New Feature Querying/Parameters & Variables Querying/Native .Completeness

I'm using a filter variable in an SQL query. The query is similar to this: ``…` sql select bla_bla from my_table as mt left join bla_bla where {{some_date_field}} ``` `some_date_field` is a variable with type "Field filter" and it's a column from `my_table`. However this filter fails in the dashboard. After some investigation, I found that Metabase generates filter's SQL code as `my_table.some_column` and not `mt.some_column` which causes a MySQL error like "Unknown column 'my_table.some_column' in 'field list'". Apparently MySQL requires using alias if an alias is defined for that table. It seems, in the menu where we define field filters, metabase should ask user how to refer to the table & column rather than what table and column to pick. Or this may be integrated into the syntax. E.g. ``` sql select bla_bla from my_table as mt left join bla_bla where {{some_date_field:mt.some_column}} ``` :arrow_down: Please click the :+1: reaction instead of leaving a `+1` or `update?` comment

cheers, Eva