supabase / etl / 39356688382

81%

Build Type

push

github

Committed by web-flow

Commit Message

bigquery: reject deferrable primary keys (#1106)

BigQuery keeps the change with the highest sequence number for each
key. When an update changes the key, ETL writes a delete for the old
key and then the new row.

With a DEFERRABLE primary key, `update t set id = id + 1` on ids 1, 2
and 3 moves 1->2, then 2->3, then 3->4. The 2->3 move deletes key 2
after row 1 moved into it, and that delete wins. BigQuery ends with
only key 4 while Postgres has 2, 3 and 4. Nothing reports an error.

Reject such tables, like ClickHouse does since #1083. The initial copy
fails the table, and a schema change that makes the key deferrable
stops the apply worker.

Coverage Stats

21 of 21 new or added lines in 1 file covered. (100.0%)

62 existing lines in 5 files now uncovered.

56009 of 69935 relevant lines covered (80.09%)

40763.48 hits per line