Re: pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2
От | Kevin Field |
---|---|
Тема | Re: pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2 |
Дата | |
Msg-id | fa51b30a-643c-4321-a341-9adc11ef1a96@s28g2000vbp.googlegroups.com обсуждение исходный текст |
Ответ на | pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2 (Kevin Field <kevinjamesfield@gmail.com>) |
Ответы |
Re: pgAgent "new step" fails for batch jobs in
pgAdmin3 1.10.0 Beta 2
|
Список | 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 по дате отправления: