Safety and cost review in Snowflake

Snowflake is read-only in Tablyne. Writes are refused before sending, and costly queries ask for confirmation first.

Tablyne handles Snowflake safety in two layers. The first is that nothing writes. The second is that expensive reads ask first.

Nothing writes

Every Snowflake connection is read-only, and the setting is fixed in the form. Tablyne reads the text of each statement before it sends anything. Only SELECT, WITH, SHOW, DESCRIBE and EXPLAIN of a read pass. Commands such as INSERT, UPDATE, DELETE, MERGE, COPY, CREATE, ALTER, DROP, CALL, USE, SET, BEGIN and GRANT are refused. The error says “Read only: this statement was rejected before submission”. Incomplete or invalid SQL is refused as well.

Because of this, there is no staged edit to review for Snowflake and no row-level conflict check. The grid never produces a write.

This guard is a check of the SQL text in Tablyne. It cannot know what a function does, so a SELECT that calls a stored procedure or advances a sequence still passes. It does not replace grants in Snowflake. Use a role that can only read.

Reads that ask first

The console confirms before it runs a query when:

  • the EXPLAIN estimate is above the connection’s threshold, which defaults to 10 GiB;
  • the cost of some statements in a script cannot be estimated;
  • the connection is tagged as production and the query would resume a suspended warehouse.

Each confirmation names the warehouse, its size and the timeout. The text is tied to the query you confirmed. If you change the SQL or the tab context after confirming, the console asks again.

The threshold is a warning. It does not stop a query that you confirm.