[pgAdmin][RM3913] pgagent run status not correct

Aditya Toshniwal <[email protected]>
Newsgroups gmane.comp.db.postgresql.pgadmin.devel
Message-ID <CAM9w-_mKVBqw=LDNfA98v8oHfNivxcE_W-oM612ttCPTg4vTaA@mail.gmail.com>
Hi Hackers,

Attached is the patch to fix the incorrect value displayed for "Running at"
for pgAgent job properties.

Kindly review.

-- 
Thanks and Regards,
Aditya Toshniwal
Sr. Software Engineer | EnterpriseDB India | Pune
"Don't Complain about Heat, Plant a TREE"
RM3913.patch (application/octet-stream, 756 B)
diff --git a/web/pgadmin/browser/server_groups/servers/pgagent/static/js/pga_job.js b/web/pgadmin/browser/server_groups/servers/pgagent/static/js/pga_job.js
index 4f719043c..6bf01c9ba 100644
--- a/web/pgadmin/browser/server_groups/servers/pgagent/static/js/pga_job.js
+++ b/web/pgadmin/browser/server_groups/servers/pgagent/static/js/pga_job.js
@@ -88,7 +88,7 @@ define('pgadmin.node.pga_job', [
           var d = pgBrowser.Node.Model.prototype.parse.apply(this, arguments);
 
           if (d) {
-            d.jobrunningat = d.jaghostagent || gettext('Not running currently.');
+            d.jobrunningat = d.jagagent || gettext('Not running currently.');
             d.jlgstatus = d.jlgstatus || gettext('Unknown');
           }
           return d;
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.