Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kiHAV-0001wj-MN for pgadmin-hackers@arkaria.postgresql.org; Thu, 26 Nov 2020 13:18:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kiHAU-00014Y-KR for pgadmin-hackers@arkaria.postgresql.org; Thu, 26 Nov 2020 13:18:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kiHAU-00013P-At for pgadmin-hackers@lists.postgresql.org; Thu, 26 Nov 2020 13:18:38 +0000 Received: from mail-qt1-x835.google.com ([2607:f8b0:4864:20::835]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kiHAR-0005LS-Dj for pgadmin-hackers@postgresql.org; Thu, 26 Nov 2020 13:18:37 +0000 Received: by mail-qt1-x835.google.com with SMTP id m65so1043349qte.11 for ; Thu, 26 Nov 2020 05:18:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=kfR/LxO67tdpmq/fEdk2dUoFf8U674fxX3LRF8ugkaQ=; b=CWm11x5Si0kjldf+xyCp9NkLrJme+uCoZEJscEiFORtfLJTIhI361p1EGpI0iIrYlh XA9DocbRr/ZDsCcFz72DrmHgMtw8TEE7lDcIjsLy1uLktc4LZxIT8p8Jxc+uqbGaBMn+ WRlkp8nYv21z7kXWeKac+P4VqiuXkRv1UBhBgfhT310knJnYuIWUhP/HkDZelVIy6j6g +UisyjjWmWfAHI8bFrmfZezd/MkIFrkBwuWFBAwJ4pkxRim64WTzUmAWM2Fy+IY7Uhp/ PrN0Yu86qd1hnOo+xK3CkWEVa5f/yskk3U0bP9SxweWmbObo9Ct8RzdGjCyBgoeKNAdP 1xuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=kfR/LxO67tdpmq/fEdk2dUoFf8U674fxX3LRF8ugkaQ=; b=khJQBwxymqh0nHgW1YzOj0l2GvgCXo0FZWkRrDAzRFjHIf40YNvi402TW1Fs8c7Xk0 XcbBkLiIeA85sbFIpJkO1WSpLn9YPwVr1hycKneT6JErbUpoWwHzJeflDjf5DKIXJJiD DwdK3qpFsMv0S0CpcOyopJEs7oLPi5j6gYPAonF8759XgQzv+nSgTTGpxsZ2HzNcT6Mk S0+UBgYLyhiLFVYezInxzd+K968etISdldiosm4EuzpTIYdf4HdJk0J5g1eeWhiqhdsd 72zOE2BOWpINDHxdgQXOMVtefAOpMjc3fBwkHaKyHyfMTVxPs9VqK6SWlkaRXZlYfP8r +XQQ== X-Gm-Message-State: AOAM532DTzH9KrEgaDO3xM8wdlRzrzWIfcNt/du+bRSgBnDIE97zWYaN kXWCQTVeik3HVjj4DuZaqlGgVzcXVZtz3hRLaG5+dvIrceA12r+8PAuSd/XSm0ad9wb02RHWyFM HZiBy48P/T0ZN1LQtKUSaekAvsbrPUqkL/tllQjPHtuIWlDhCA8tJkZu+v9hou9Q9VSXfF3uJ1F T2V4o991rzlODXF84UKWbV5bkoIkf4UFvySPcHD8qtMZaQyREeMrDScGblWGiZud0S9pz4lTc= X-Google-Smtp-Source: ABdhPJxcX8ZWOS+L6VptQYGqJhGjpqQZ4cJ1pQKZrrl7ng4qOs5rfKK5O9WJY6P8pyyz9qANEjkTn7Wh05W9ku1h/I0= X-Received: by 2002:ac8:370e:: with SMTP id o14mr3007626qtb.195.1606396712241; Thu, 26 Nov 2020 05:18:32 -0800 (PST) MIME-Version: 1.0 From: Rahul Shirsat Date: Thu, 26 Nov 2020 18:47:56 +0530 Message-ID: Subject: Unable to download macros query results (reference #RM5965) To: pgadmin-hackers Content-Type: multipart/alternative; boundary="00000000000066ebc705b50261d2" X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --00000000000066ebc705b50261d2 Content-Type: text/plain; charset="UTF-8" Hi Team, Users are unable to download macros query results. *Lets look out how download query result button works:* For pgadmin4, always downloads the latest query result when the user makes n-number of sql changes in the query tool, no need to execute, download takes care of it. Does not work with macros as query is needed in the query tool, which macros does not provide (While feature implementation, it was decided that macros query won't be added to the query tool, as users may lose any important queries in it). In pgadmin3, always the last executed query result gets downloaded even if the user makes n-number of sql changes in the query tool. Works with macros. For the latest query change results, the user has to first execute before every download. For Macros, with the pgadmin4 approach, even if we implement a download option, it would be difficult to decide whether to download the already ran macros or to download the query result present in the query tool. Please suggest. -- *Rahul Shirsat* Senior Software Engineer | EnterpriseDB Corporation. --00000000000066ebc705b50261d2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team,

Users are unable to download m= acros query results.

Lets look out how downl= oad query result button works:

For pgadmin4,=C2=A0always d= ownloads the latest query result when the user makes n-number of sql change= s=C2=A0in the query tool, no need to execute, download takes care of it. Do= es not work with macros as query is needed in the query tool, which macros = does not provide (While feature implementation, it was decided that macros = query won't be added to the query tool, as users may lose any important= queries in it).

In pgadmin3, always the last execu= ted query result gets downloaded even if the user makes n-number of sql cha= nges=C2=A0in the query tool. Works with macros. For the latest query change= results, the user has to first execute before every download.
For Macros, with the pgadmin4 approach, even if we implement a= download option, it would be difficult=C2=A0to decide whether to download = the already ran macros or to download the query=C2=A0result present in the = query tool.

Please suggest.

--
Rahul Shirsat
Senior So= ftware Engineer=C2=A0|=C2=A0EnterpriseDB=C2=A0Corporation.
--00000000000066ebc705b50261d2--