From f656bd57eee83ec0ff6ee2d5dd0c38b97e0e162d Mon Sep 17 00:00:00 2001 From: Phillip Cloud <417981+cpcloud@users.noreply.github.com> Date: Tue, 13 Jun 2023 10:48:00 -0400 Subject: [PATCH] fix(clickhouse): use the correct dialect to generate subquery string for Contains operation --- ibis/backends/clickhouse/compiler/values.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ibis/backends/clickhouse/compiler/values.py b/ibis/backends/clickhouse/compiler/values.py index 52862e8ae479..46b14c3581ff 100644 --- a/ibis/backends/clickhouse/compiler/values.py +++ b/ibis/backends/clickhouse/compiler/values.py @@ -850,9 +850,9 @@ def tr(op, *, cache, **kw): # annoying to detect so we let it through to enable the # uncorrelated use case (pandas-style `.isin`) subquery = translate(options.to_expr().as_table().op(), {}) - right_arg = f"({subquery})" + right_arg = f"({_sql(subquery)})" else: - right_arg = translate_val(options, cache=cache, **kw) + right_arg = _sql(translate_val(options, cache=cache, **kw)) # we explicitly do NOT parenthesize the right side because it doesn't # make sense to do so for Sequence operations