The #299 PR took care of bacward compatibility of the function, but there is still one problem left. If extension isn't updated type of the jobname field in the cron.job table is still NAME, and as a result scan was failing to find rows and unschedule a named job.
This fix is relying on the fact that SQL API of the unschedule() function is updated consistently with the cron.job table definition.
The #299 PR took care of bacward compatibility of the function, but there is still one problem left. If extension isn't updated type of the jobname field in the cron.job table is still NAME, and as a result scan was failing to find rows and unschedule a named job.
This fix is relying on the fact that SQL API of the unschedule() function is updated consistently with the cron.job table definition.