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

From Kevin Field
Subject Re: pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2
Date
Msg-id fa51b30a-643c-4321-a341-9adc11ef1a96@s28g2000vbp.googlegroups.com
Whole thread Raw
In response to pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2  (Kevin Field <kevinjamesfield@gmail.com>)
Responses Re: pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2  (Dave Page <dpage@pgadmin.org>)
List pgadmin-hackers
> 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', , ;

Also that <StpId> is a problem if you try to copy this out and run the
query manually, which I had to do because when I unchecked "read only"
and edited it to get rid of the last two parameters, I got the same
error message about commas, leading me to think that what I saw on the
screen was not what actually got sent to the db server by pgAdmin (so
I'm not sure what the benefit is to being able to edit it there, if
you have to open a query window to actually execute your edited
version anyway.)  But when I took out "jstid, " and "<StpId>, " in
addition, it worked.

Forgot to mention, I'm on win32.

pgadmin-hackers by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Problems getting in touch with some translators
Next
From: Heikki Linnakangas
Date:
Subject: Re: Problems getting in touch with some translators