tapdb: drop and re-create genesis_info_view

tapdb/sqlc/migrations/000002_assets.up.sql

@@ -315,7 +315,7 @@ CREATE TABLE IF NOT EXISTS asset_seedlings (
 CREATE VIEW genesis_info_view AS
     SELECT
         gen_asset_id, asset_id, asset_tag, assets_meta.meta_data_hash meta_hash,
-        output_index, asset_type, genesis_points.prev_out prev_out, 
+        output_index, asset_type, genesis_points.prev_out prev_out,
         chain_txns.txid anchor_txid, block_height
     FROM genesis_assets
     -- We do a LEFT JOIN here, as not every asset has a set of

tapdb/sqlc/migrations/000012_anchor_txid.down.sql

@@ -0,0 +1 @@
+DROP VIEW IF EXISTS genesis_info_view;

tapdb/sqlc/migrations/000012_anchor_txid.up.sql

@@ -0,0 +1,22 @@
+DROP VIEW IF EXISTS genesis_info_view;
+
+-- This view is used to fetch the base asset information from disk based on
+-- the raw key of the batch that will ultimately create this set of assets.
+-- To do so, we'll need to traverse a few tables to join the set of assets
+-- with the genesis points, then with the batches that reference this
+-- points, to the internal key that reference the batch, then restricted
+-- for internal keys that match our main batch key.
+CREATE VIEW genesis_info_view AS
+    SELECT
+        gen_asset_id, asset_id, asset_tag, assets_meta.meta_data_hash meta_hash,
+        output_index, asset_type, genesis_points.prev_out prev_out,
+        chain_txns.txid anchor_txid, block_height
+    FROM genesis_assets
+    -- We do a LEFT JOIN here, as not every asset has a set of
+    -- metadata that matches the asset.
+    LEFT JOIN assets_meta
+        ON genesis_assets.meta_data_id = assets_meta.meta_id
+    JOIN genesis_points
+        ON genesis_assets.genesis_point_id = genesis_points.genesis_id
+    LEFT JOIN chain_txns
+        ON genesis_points.anchor_tx_id = chain_txns.txn_id;