Re: [pgAdmin4][debugger]: RM #1354 & RM #1323 - Mailing list pgadmin-hackers

From Dave Page
Subject Re: [pgAdmin4][debugger]: RM #1354 & RM #1323
Date
Msg-id CA+OCxoxv1QhLZhdM0FaK5qDuZGZ7S_Naw2kEgJM+i-aNJmfXxg@mail.gmail.com
Whole thread Raw
In response to Re: [pgAdmin4][debugger]: RM #1354 & RM #1323  (Neel Patel <neel.patel@enterprisedb.com>)
Responses Re: [pgAdmin4][debugger]: RM #1354 & RM #1323  (Neel Patel <neel.patel@enterprisedb.com>)
List pgadmin-hackers
Hi

On Sun, Jun 19, 2016 at 5:50 PM, Neel Patel <neel.patel@enterprisedb.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


pgadmin-hackers by date:

Previous
From: Murtuza Zabuawala
Date:
Subject: PATCH: To fixed the issue in Materialized view (pgAdmin4)
Next
From: Dave Page
Date:
Subject: Re: Fixed RM #1356