cannot scan NULL into *string #725
Description
On PG18.0 using Windows Server 2019 64bit, I went from pg_timetable v5.13.0 to v6.0.0 using /UPGRADE which was successful.
Now all of the scheduled tasks don't run. The error is...
2025-11-03 11:30:18.524�[32m [INFO] [chain:2] �[0mStarting chain
2025-11-03 11:30:18.529�[31m [ERROR] [chain:2] [sql:SELECT task_id, command, kind, run_as, ignore_error, autonomous, database_connection, timeout
FROM timetable.task WHERE chain_id = $1 ORDER BY task_order ASC] [args:[2]] [err:can't scan into dest[3] (col: run_as): cannot scan NULL into *string] [pid:14600] [time:2.6425ms] �[0mQuery
2025-11-03 11:30:18.530�[31m [ERROR] [chain:2] [error:can't scan into dest[3] (col: run_as): cannot scan NULL into *string] [vxid:55834575634] �[0mFailed to retrieve chain elements
Looking at [select * from timetable.log order by ts desc] I see...
It looks like it has issues if run_as column is NULL, however, when I look at the reference here
https://cybertec-postgresql.github.io/pg_timetable/v6.x/yaml-format/?h=run_as#chain-level
...it says that run_as column default is NULL.
When I downgrade pg_timetable to v5.13.0 all the tasks run successfully.