pgAgent bugs? - Mailing list pgadmin-hackers

From Roberts, Jon
Subject pgAgent bugs?
Date
Msg-id 15362F202C62EA4590F5F3E5FA15021E0528678C@nasappexc04.int.asurion.com
Whole thread Raw
Responses Re: pgAgent bugs?
List pgadmin-hackers
In job.cpp, it has this code to get the next job step:

    DBresult *steps=threadConn->Execute(
        wxT("SELECT jstid, jstkind, jstdbname, jstcode, jstonerror ")
        wxT("  FROM pgagent.pga_jobstep ")
        wxT(" WHERE jstenabled ")
        wxT("   AND jstjobid=") + jobid +
        wxT(" ORDER BY jstname, jstid"));

If I had a job with step 1 called Zebra and step 2 called Apple, the above
query would get and then execute step 2 first because of the order by
clause.

I also noticed with version 1.8 of the UI, if I change the On Error flags,
nothing seems to happen.  If I insert a new step, I can make it Succeed,
Fail, or Ignore but changes to this field using pgAdmin after the step has
been created are ignored.


Jon

pgadmin-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: Using pgAdmin and pgAgent with Greenplum
Next
From: svn@pgadmin.org
Date:
Subject: SVN Commit by dpage: r6793 - in trunk/pgadmin3: . pgadmin/agent