tapdb: fix comments on ON CONFLICT

lightninglabs · Aug 4, 2023 · 735cb1d · 735cb1d
1 parent bd500c9
commit 735cb1d
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/tapdb/sqlc/assets.sql.go b/tapdb/sqlc/assets.sql.go
diff --git a/tapdb/sqlc/queries/assets.sql b/tapdb/sqlc/queries/assets.sql
@@ -159,6 +159,7 @@ INSERT INTO asset_group_sigs (
 ) VALUES (
     $1, $2, $3
 ) ON CONFLICT (gen_asset_id)
+    -- This is a NOP, gen_asset_id is the unique field that caused the conflict.
     DO UPDATE SET gen_asset_id = EXCLUDED.gen_asset_id
 RETURNING sig_id;
 
@@ -173,7 +174,6 @@ INSERT INTO genesis_assets (
 ) VALUES (
     $2, $3, (SELECT meta_id FROM target_meta_id), $4, $5, $6
 ) ON CONFLICT (asset_id)
-    -- This is a NOP, asset_tag is the unique field that caused the conflict.
     -- This is a NOP, asset_id is the unique field that caused the conflict.
     DO UPDATE SET asset_id = EXCLUDED.asset_id
 RETURNING gen_asset_id;