Schema Commentary Invalidates Setup

[larron]

-- Some comment here in your schema.sql file will cause substreams-sink-sql setup $DSN ./substreams.yaml to fail with something like:

substreams-sink-sql setup $DSN ./substreams.yaml
2025-08-01T04:36:10.832+0800 INFO (pipeline) computed start block {"module_name": "map_program_data", "start_block": 0}
2025-08-01T04:36:10.832+0800 INFO (pipeline) computed start block {"module_name": "db_out", "start_block": 0}
2025-08-01T04:36:10.833+0800 INFO (sink-sql) created new DB loader {"batch_block_flush_interval": 0, "batch_row_flush_interval": 0, "live_block_flush_interval": 0, "on_module_hash_mismatch": "Error", "handle_reorgs": false, "dialect": "*db.ClickhouseDialect"}                                                                                                                                                               
setup: exec userSql: exec schemaName: code: 62, message: Empty query

Currently testing with ClickHouse as seen in the log. (Have not tested this with a PG DB).

[GabrielCartier]

Heads up: this repository is deprecated (see #133). The SQL sink was folded into the main substreams CLI as substreams sink postgres / substreams sink clickhouse, shipped in substreams v1.20.2. This repo gets security fixes only for one year, then goes read-only.

Leaving this open because the bug is real and the code still runs — it just lives at sink/sql/db_changes/ in streamingfast/substreams now. Any fix has to land there, so please refile or follow up upstream if you are still hitting it.