Not sure if there is a better way to report this. Seems like postgres is writing notices to standard error which is causing the task to report that zero files were run correctly. Maybe differentiate between those run with errors, run with warnings, and those run cleanly???
Running "run-sql:create-local-db" (run-sql) task
>> Correctly run 1 files.
Running "run-sql:create-local-tables" (run-sql) task
>> psql:sql/create_tables.sql:11: NOTICE: table "xxxxx" does not exist, skipping
>> psql:sql/create_tables.sql:21: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "xxxxxx_pkey" for table "xxxxx"
>> psql:sql/create_tables.sql:21: NOTICE: CREATE TABLE / UNIQUE will create implicit index "xxxxxx_text_key" for table "xxxxx"
>> psql:sql/create_tables.sql:21: NOTICE: CREATE TABLE / UNIQUE will create implicit index "xxxxx_title_key" for table "xxxxxx"
>> psql:sql/create_tables.sql:29: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "xxxxx_pkey" for table "xxxxx"
>> Correctly run 0 files.
Done, without errors.
Not sure if there is a better way to report this. Seems like postgres is writing notices to standard error which is causing the task to report that zero files were run correctly. Maybe differentiate between those run with errors, run with warnings, and those run cleanly???