If you pick Batch rather than SQL for "Kind", you naturally can't edit the database or connection string, but the SQL generated has commas and blanks (i.e., nothing, not even an empty string) for those columns, and so fails:
INSERT INTO pgagent.pga_jobstep (jstid, jstjobid, jstname, jstdesc, jstenabled, jstkind, jstonerror, jstcode, jstdbname, jstconnstr) SELECT <StpId>, 5, E'C:\\mybat.bat', '', true, 'b', 'f', E'C:\ \mybat.bat', , ; With those options selected it should either put nulls or get rid of the commas and the ", jstdname, jstconnstr", right? -- Sent via pgadmin-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers
