pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2 - Mailing list pgadmin-hackers

From Kevin Field
Subject pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2
Date
Msg-id 7edf31c3-c3fe-4faf-92b4-4d56dface86e@j12g2000vbl.googlegroups.com
Whole thread Raw
Responses Re: pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2  (Dave Page <dpage@pgadmin.org>)
List pgadmin-hackers
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?

pgadmin-hackers by date:

Previous
From: svn@pgadmin.org
Date:
Subject: SVN Commit by guillaume: r7834 - trunk/pgadmin3/i18n/zh_TW
Next
From: Guillaume Lelarge
Date:
Subject: Problems getting in touch with some translators