Re: [pgAdmin][RM3913] pgagent run status not correct - Mailing list pgadmin-hackers

From Dave Page
Subject Re: [pgAdmin][RM3913] pgagent run status not correct
Date
Msg-id CA+OCxowUoj_+=DpvjeExzmZUcYJ3cUeWfmiTQqKhcRj+NArh6Q@mail.gmail.com
Whole thread Raw
In response to [pgAdmin][RM3913] pgagent run status not correct  (Aditya Toshniwal <aditya.toshniwal@enterprisedb.com>)
List pgadmin-hackers
Thanks, applied.

On Wed, Oct 23, 2019 at 2:28 PM Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> wrote:
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"


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgadmin-hackers by date:

Previous
From: Dave Page
Date:
Subject: pgAdmin 4 commit: Ensure the correct "running at" agent is shown when a
Next
From: Dave Page
Date:
Subject: pgAdmin 4 commit: Don't quote bigints when copying them from the Query