sqlc/migrations: add new unique key to assets table

Fixes #691 by adding a unique constraint that will actually work. The assumption of the constraint is that there will never be an asset of the same asset ID with the same script key in the same anchor transaction output. This would be impossible anyway because the asset leaves would collide within the asset-level MS-SMT tree. So this unique key is safe to use as an upsert detection mechanism.
lightninglabs · Jun 24, 2024 · 1453a71 · 1453a71
1 parent 651af43
commit 1453a71
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 0 deletions.
diff --git a/tapdb/sqlc/migrations/000020_asset_unique_key.down.sql b/tapdb/sqlc/migrations/000020_asset_unique_key.down.sql
@@ -0,0 +1 @@
+DROP INDEX IF EXISTS assets_genesis_id_script_key_id_anchor_utxo_id_unique;
diff --git a/tapdb/sqlc/migrations/000020_asset_unique_key.up.sql b/tapdb/sqlc/migrations/000020_asset_unique_key.up.sql
@@ -0,0 +1,4 @@
+CREATE UNIQUE INDEX assets_genesis_id_script_key_id_anchor_utxo_id_unique
+ON assets (
+    genesis_id, script_key_id, anchor_utxo_id
+);
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		DROP INDEX IF EXISTS assets_genesis_id_script_key_id_anchor_utxo_id_unique;