From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Kevin Field <kevinjamesfield(at)gmail(dot)com> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2 |
Date: | 2009-05-05 12:17:06 |
Message-ID: | 937d27e10905050517u4a1ff1f4v210d1eb9e623054a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Mon, May 4, 2009 at 6:25 PM, Kevin Field <kevinjamesfield(at)gmail(dot)com> wrote:
> 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?
That was fixed here:
http://svn.pgadmin.org/cgi-bin/viewcvs.cgi?rev=7800&view=rev
It'll be in beta 2.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2009-05-05 12:20:01 | Re: pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2 |
Previous Message | svn | 2009-05-05 11:18:52 | SVN Commit by dpage: r7844 - trunk/pgadmin3/pgadmin/include/frm |