Skip to main content
Enterprise only
Use backticks around column names in SQL expressions when you need to preserve case or include spaces. Backticks work in both Enterprise SQL statements and table SDK expression strings. Use single quotes for SQL string literals, and pass bare column names as the keys of values and values_sql.
Double quotes have different meanings across these interfaces. In SQL statements, "averageRating" is a column reference. In values_sql expressions it is a string literal, so "averageRating" + 0.1 fails with an error such as Cannot coerce arithmetic expression Utf8 + Float64 to valid types. Some SDK filter paths also accept double-quoted identifiers; use backticks to keep the same spelling across filters and update expressions.

Preserve camelCase names in SQL

SQL lowercases unquoted identifiers. If your table has a column named movieId, SELECT movieId FROM movies looks for movieid and fails. Quote each column reference to preserve its exact name:
Backticks work in the same query:
Apply the same rule inside the SELECT query of a materialized view definition.

Update columns and filter rows with the SDK

The following examples assume movies has numeric columns movieId, averageRating, and numVotes, and a string column reviewStatus. Use backticks for column references inside both where and values_sql expression strings:
The dictionary key "averageRating" contains only the column name. Its enclosing quotes are Python syntax. A key such as '"averageRating"' or "`averageRating`" includes SQL quote characters in the name and fails because that column does not exist. For a constant value, use values and pass the Python value directly:
With values_sql, write the constant as a SQL string literal instead:
The outer double quotes delimit a Python string; the inner single quotes are part of the SQL expression.