Bind variables: No longer ignored as parameters for some built-in table functions¶

In Snowflake Scripting, a driver, or the SQL REST API, you can use bind variables in SQL statements. (For examples of using bind variables, see Using a variable in a SQL statement (binding), Binding data, and Using bind variables in a statement.

This behavior change affects cases in which you pass a bind variable directly as one of the built-in table function arguments listed below. The behavior changes in the following way:

Before the change:

The bind variable is ignored, and the argument is not passed to the table function.

AFter the change:

The bind variable is passed as an argument to the table function.

Note that this does not affect cases in which you pass a bind variable to another function before passing the result to a table function argument. For example, if you are calling the COPY_HISTORY function, this change affects cases in which you pass a bind variable directly as the START_TIME argument:

COPY_HISTORY( START_TIME=> ?, ...

This does not affect cases in which you pass the bind variable to another built-in function first:

COPY_HISTORY( START_TIME=> DATEADD('days', ?, ...

If you want to preserve the behavior before the change, you can rewrite your code to avoid passing the argument that uses the bind variable. For example, if you are calling the TASK_HISTORY function and you do not want the results filtered by a specific task, omit the TASK_NAME argument from the call.

The following table function arguments are affected by this change:

Ref: 1410