Re: [pgAdmin4][debugger]: RM #1354 & RM #1323

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Neel Patel <neel(dot)patel(at)enterprisedb(dot)com>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: [pgAdmin4][debugger]: RM #1354 & RM #1323
Date: 2016-06-20 08:38:48
Message-ID: CA+OCxoxv1QhLZhdM0FaK5qDuZGZ7S_Naw2kEgJM+i-aNJmfXxg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi

On Sun, Jun 19, 2016 at 5:50 PM, Neel Patel <neel(dot)patel(at)enterprisedb(dot)com> wrote:
> Hi Dave,
>
> make sense. We should ensure that operations happen sequentially.
> Please find attached patch file for the fix.

Hmm, using synchronous calls is not an option either. They're strongly
discouraged, and will throw warnings on some browsers.

Can we not just have the first callback initiate the next call and so on?

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

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

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2016-06-20 08:42:50 Re: Fixed RM #1356
Previous Message Murtuza Zabuawala 2016-06-20 08:03:04 PATCH: To fixed the issue in Materialized view (pgAdmin4)