Cost guard and safety in BigQuery

BigQuery is read-only in Tablyne. A mandatory dry run, a byte cap on every job and typed confirmations guard the cost.

Tablyne protects BigQuery in two ways. It does not write, and it limits what a read can cost.

No writes

The connection is read-only, and the form shows it as fixed. Tablyne checks the text before anything is sent. INSERT, UPDATE, DELETE, MERGE and DDL are refused, and so are EXECUTE IMMEDIATE, CALL and transactions inside a script. The banner also reminds you to use a read-only role on the project, because the check in Tablyne is a safeguard and not a permission.

There is no staged edit or conflict check, since the grid never writes.

The cost gate

All queries pass through one gate in the app, and no other part of the BigQuery code builds a query job.

  1. The text must be a read. Otherwise it is refused before any request.
  2. A dry run is required. It has no skip button. If the dry run fails, the query does not run, and you see the server’s error.
  3. The server’s statement type must be SELECT, or a script that Tablyne already checked locally.
  4. Every job carries a maximumBytesBilled limit. BigQuery refuses the job again if it would read more.

The confirmation you give is tied to the exact text and the cap. If the text changes after you confirm, the console asks you to run it again.

Limits of the guard

The dry run of a script validates only up to the first control-flow statement, so a script never counts as fully estimated. The daily spend warning reads the job history. If it cannot read all of it, the console says the warning cannot be guaranteed. Cancelling a job asks BigQuery to stop, and the job may have billed until it did.