Skip site navigation (1) Skip section navigation (2)

pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2

From: Kevin Field <kevinjamesfield(at)gmail(dot)com>
To: pgadmin-hackers(at)postgresql(dot)org
Subject: pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2
Date: 2009-05-04 17:25:53
Message-ID: 7edf31c3-c3fe-4faf-92b4-4d56dface86e@j12g2000vbl.googlegroups.com (view raw or flat)
Thread:
Lists: 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?

Responses

pgadmin-hackers by date

Next:From: Kevin FieldDate: 2009-05-04 17:31:44
Subject: Re: pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2
Previous:From: svnDate: 2009-05-03 19:49:04
Subject: SVN Commit by guillaume: r7834 - trunk/pgadmin3/i18n/zh_TW

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group