{
  "id": 19692956,
  "title": "BigQuery MERGE Is Not a Uniqueness Constraint: A Replay-Safe Tutorial",
  "url": "https://urgent.news/2026/11/12/bigquery-merge-is-not-a-uniqueness-constraint-a-replay-safe-tutorial",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-12T19:17:18.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/saravanan_techx/bigquery-merge-is-not-a-uniqueness-constraint-a-replay-safe-tutorial-32a4"
  },
  "original_language": "en",
  "account": null,
  "summary": "A MERGE can be atomic and still leave duplicate business keys. The missing ingredient is a clear key and version contract. This tutorial builds a current-state orders table, not an event-history table. One row represents one order_id . It assumes a single writer and a source-provided, monotonically increasing integer version per order. Timestamps alone are not that contract. Why the obvious MERGE…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}