Hi, the recent IN function isn’t actually an IN function, it’s an OR, therefore offer no real difference to just pasting in a batch of values to the standard IS filter.
Performance is obviously poor as the SQL is converted to an OR statement, so always just default back to using raw SQL.
Is this just me or am I misunderstanding the IN function?
Are you talking about the recent feature adding a SQL variable representing a multiple-select filter that can be used in WHERE .. IN (), like
WHERE col IN ({{variable}})
?
(EDIT:) This is a new feature in Metabase 56 that allows multi-select filters in native queries. Previously, you could only use single-valued variables.
Performance will depend on your database engine, but most have optimizations for large lists, converting them to JOINs on temporary tables.
Are you seeing performance issues with this construct? If so, what database engine and version are you running?