Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1anLvc-0000qS-Of for pgadmin-hackers@arkaria.postgresql.org; Tue, 05 Apr 2016 08:01:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1anLvc-0001TA-BW for pgadmin-hackers@arkaria.postgresql.org; Tue, 05 Apr 2016 08:01:36 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1anLvO-0000jf-0h for pgadmin-hackers@postgresql.org; Tue, 05 Apr 2016 08:01:22 +0000 Received: from mail-io0-x230.google.com ([2607:f8b0:4001:c06::230]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1anLvJ-0002nV-AC for pgadmin-hackers@postgresql.org; Tue, 05 Apr 2016 08:01:20 +0000 Received: by mail-io0-x230.google.com with SMTP id g185so9920167ioa.2 for ; Tue, 05 Apr 2016 01:01:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BJqPIPN9YNSFbPobYV0RP4wyDoY8UUuQJ2BBA1quReM=; b=tOuxJB664kB+4Og/r60JVPbYJ9yVvsdPeITZsLySE7w+B/9HR4teyyIWDlmA3GA8c+ aa/MjpjsM5E/sEkwx3OAcv5kD0zAhAak3eJLIn5UxsWw6tgGJubjWE4lrgrCRkiCqSrF pDYT2dNFcwl74XXorXlfNaZXLaBN6u6w+XbO7kmqnDWyEBY0MPzNmNf0lr2+qEl1VPiS qCrJqHhTOtFLk//8CcCz5jjkTxSpDoE1pXXNEOCCJKGoA9MbKQjg5hajVkwjY9WkbHyR kx5GsK/jpMcpPQ7MsKhgAXxSd/QMa0E5ShTnfcQl89QOJcDfVg3UFBNe+zQMzTYkdb2G j2WQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=BJqPIPN9YNSFbPobYV0RP4wyDoY8UUuQJ2BBA1quReM=; b=Uo2H4YHlbPuzjM1ghl9tNApFFOEsCGGKPdvNNmGIenevFyP7Kig3FNWzdtUhcW1jI9 4kQMYfJ2gfDcmnkGzxu1l8EH/Gu5W8bTl62dlzHK8vQ/txL3yIr9agAliEdq5XwCkkl+ OgoYN1IGq9k56VrSY6tW8uv0ru2Zaybui+cGzY1MdLiY3uGF11q+zye4G7jzV2uuI6wo YDaVSbSwlQ96S+hitaRKEf908CSDJz49i+EPM2rr2++SSy3twO4cIItyIKIbOXyj/4U/ nklxokvl66yG3NApq88D9AcoI8Wr1jfpEFA55bhMMskq1kPcFoL06FmNeEIhxbuE01ZQ 5gzQ== X-Gm-Message-State: AD7BkJIOXAPUoBf7hJTXKzp7YZc4Iuno8zKpH6D5RwvbrXcx0T/OrNw/DW8HIFUyFZmW4RzCdXCyfSHZ5OUW8pli X-Received: by 10.107.156.193 with SMTP id f184mr6624112ioe.117.1459843276442; Tue, 05 Apr 2016 01:01:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.39.5 with HTTP; Tue, 5 Apr 2016 01:00:56 -0700 (PDT) In-Reply-To: References: From: Ashesh Vashi Date: Tue, 5 Apr 2016 13:30:56 +0530 Message-ID: Subject: Re: [pgAdmin4][psycopg2] - Modified status message implementation To: Neel Patel Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary=001a1140cd38ebaecf052fb83fbd X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --001a1140cd38ebaecf052fb83fbd Content-Type: text/plain; charset=UTF-8 On Mon, Apr 4, 2016 at 4:53 PM, Neel Patel wrote: > Hi, > > Please find attached patch file which modified the earlier statusmessage > implementation. > > *Previous implementation:- * > > statusmessage was implemented inside the poll function and if poll result > row is greater than zero then statusmessage was replaced by the result row > returned so if user wants the statusmessage along with returned rows then > current implementation will not work. > > *Changes:-* > > Now "status_message()" function is implemented to get the status message > returned by last command executed on the server and removed from the poll > function. > If user wants to status messages then they have to call "status_message()" > which will return the status message text. > > Do review it and let us know for any comments. > Thanks - committed! We still need to make it work with the synchronous connection. -- Thanks & Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Company *http://www.linkedin.com/in/asheshvashi* > > Thanks, > Neel Patel > > > -- > Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-hackers > > --001a1140cd38ebaecf052fb83fbd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Mon, Apr 4, 2016 at 4:53 PM, Neel Patel <neel.patel@ente= rprisedb.com> wrote:

Hi,

= Please find attached patch file which modified the earlier statusmessage im= plementation.

Previous implementation:-=C2=A0

statusmessage was implemented inside the poll f= unction and if poll result row is greater than zero then statusmessage was = replaced by the result row returned so if user wants the statusmessage alon= g with returned rows then current implementation will not work.
<= br>
Changes:-

Now "status_me= ssage()" function is implemented to get the status message returned by= last command executed on the server and removed from the poll function.
If user wants to status messages then they have to call "statu= s_message()" which will return the status message text.

=
Do review it and let us know for any comments.
Thanks - committed!

We still need to m= ake it work with the synchronous connection.

--

Thanks & Regards,

A= shesh Vashi
EnterpriseDB INDIA:=C2=A0Enterprise PostgreSQL Company


=
Thanks,
Neel Patel


--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers=


--001a1140cd38ebaecf052fb83fbd--