Re: [pgAdmin4][Patch]: Allow user to cancel long running queries from dashboard

2-3 days is a lot of valuable engineering time. Is this a 'drop everything now' kind of feature or can this wait for some user validation on a mock up first? > On Jul 24, 2017, at 20:41, Murtuza Zabuawala > wrote: > > Sure. > > RM created:

Re: [pgAdmin4][Patch]: Allow user to cancel long running queries from dashboard

-- *Harshal Dhumal* *Sr. Software Engineer* EnterpriseDB India: http://www.enterprisedb.com The Enterprise PostgreSQL Company On Mon, Jul 24, 2017 at 8:11 PM, Dave Page wrote: > > > On Mon, Jul 24, 2017 at 3:28 PM, Shirley Wang wrote: > >> 2-3 days is a

Re: [pgAdmin4][Patch]: Allow user to cancel long running queries from dashboard

> > > On Mon, Jul 24, 2017 at 8:11 PM, Dave Page wrote: > >> >> >> On Mon, Jul 24, 2017 at 3:28 PM, Shirley Wang wrote: >> >>> 2-3 days is a lot of valuable engineering time. Is this a 'drop >>> everything now' kind of feature or can this wait for some user

Re: [pgAdmin4][Patch]: Improvise the treeview element selection

On Mon, Jul 24, 2017 at 8:51 AM, Shirley Wang wrote: > Hi Surinder, > > This change seems to be different from the other patterns for selected / > highlighted options. Is there a reason why this needs to be more visible > than it already is? In terms of feedback on the tree, we

Re: [pgAdmin4][Patch]: Improvise the treeview element selection

Hi Surinder, This change seems to be different from the other patterns for selected / highlighted options. Is there a reason why this needs to be more visible than it already is? In terms of feedback on the tree, we have not heard any pains from users that this is not visible enough. Shirley On

Re: [pgAdmin4][Patch]: Allow user to cancel long running queries from dashboard

Hi Dave, On Mon, Jul 24, 2017 at 4:44 PM, Dave Page wrote: > Thanks, applied. > > How much effort do you think it would take to turn the table into a > subnode control so we can show the SQL query and other missing fields from > pg_stat_activity on that tab? > I think around

Re: [pgAdmin4][Patch]: Allow user to cancel long running queries from dashboard

Sure. RM created: https://redmine.postgresql.org/issues/2597. On Mon, Jul 24, 2017 at 6:04 PM, Dave Page wrote: > > > On Mon, Jul 24, 2017 at 1:12 PM, Murtuza Zabuawala enterprisedb.com> wrote: > >> Hi Dave, >> >> On Mon, Jul 24, 2017 at 4:44 PM, Dave

Re: [pgAdmin4][Patch]: Allow user to cancel long running queries from dashboard

Hi Dave, Please find updated patch. On Tue, Jul 18, 2017 at 8:05 PM, Murtuza Zabuawala wrote: > Hi Shirley, > > On Tue, Jul 18, 2017 at 1:21 AM, Shirley Wang wrote: > >> Hi! >> >> I can't seem to get the patch to completely work on my

Re: [pgadmin-hackers][patch]

Thanks, applied. On Fri, Jul 21, 2017 at 10:38 PM, Joao De Almeida Pereira < jdealmeidapere...@pivotal.io> wrote: > Hi hackers, > With the last commits, the behavior of focusing on a selected entry when > entering the History Tab was not working as expected. > This patch will bring this behavior

[RM2579][pgAdmin4] Set default file listing layout as list instead of grid

Hi, Please find attached patch to set default layout of file listing as a list in file manager. Also replaced alertify with out custom alertifywrapper in file manager utils.js -- *Harshal Dhumal* *Sr. Software Engineer* EnterpriseDB India: http://www.enterprisedb.com The Enterprise PostgreSQL

Jenkins build is back to normal : pgadmin4-master-python36 #257

See

pgAdmin 4 commit: Allow queries to be cancelled from the dashboards. Fi

Allow queries to be cancelled from the dashboards. Fixes #1812 Branch -- master Details --- https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=617e9dbb3a466507a7cfdd6ba144c0dca5955dec Author: Murtuza Zabuawala Modified Files

Re: [pgAdmin4][Patch]: Allow user to cancel long running queries from dashboard

Thanks, applied. How much effort do you think it would take to turn the table into a subnode control so we can show the SQL query and other missing fields from pg_stat_activity on that tab? On Mon, Jul 24, 2017 at 11:45 AM, Murtuza Zabuawala < murtuza.zabuaw...@enterprisedb.com> wrote: > Hi