On Mon, May 4, 2009 at 6:25 PM, Kevin Field <[email protected]> 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 -- Sent via pgadmin-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers
