lnd: skip network validation when migrations are skipped

Skip the chain_params network check when startup is explicitly
configured to skip SQL migrations. In that mode the schema is assumed
to already be managed externally, and the chain_params table may not
exist yet. Avoid failing startup on a missing table in this path.

Author: ziggie1984

config_builder.go

@@ -1248,15 +1248,26 @@ func (d *DefaultDatabaseBuilder) BuildDatabase(
 		// (e.g. mainnet → testnet), which would otherwise lead to
 		// silent data corruption. This check applies to all native SQL
 		// backends.
-		chainParamsStore := chainparams.NewStore(baseDB)
-		err = chainParamsStore.ValidateNetwork(
-			ctx, d.cfg.ActiveNetParams.Params,
-		)
-		if err != nil {
-			cleanUp()
-			d.logger.Error(err)
+		//
+		// If migrations are explicitly skipped, we also skip this check
+		// because the chain_params table may not exist yet. We check
+		// only the active backend's flag since only one backend is
+		// used at a time.
+		skipMigrations := d.cfg.DB.Sqlite.SkipMigrations
+		if d.cfg.DB.Backend == lncfg.PostgresBackend {
+			skipMigrations = d.cfg.DB.Postgres.SkipMigrations
+		}
+		if !skipMigrations {
+			chainParamsStore := chainparams.NewStore(baseDB)
+			err = chainParamsStore.ValidateNetwork(
+				ctx, d.cfg.ActiveNetParams.Params,
+			)
+			if err != nil {
+				cleanUp()
+				d.logger.Error(err)
 
-			return nil, nil, err
+				return nil, nil, err
+			}
 		}
 
 		// Create the invoice store.