Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7Xo9-0068nW-C8 for pgadmin-hackers@arkaria.postgresql.org; Thu, 16 May 2024 09:53:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s7Xo9-004qMG-Gq for pgadmin-hackers@arkaria.postgresql.org; Thu, 16 May 2024 09:53:53 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7Xo9-004qIX-8v for pgadmin-hackers@lists.postgresql.org; Thu, 16 May 2024 09:53:53 +0000 Received: from mail-lj1-x22c.google.com ([2a00:1450:4864:20::22c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s7Xo6-000Tfl-JG for pgadmin-hackers@postgresql.org; Thu, 16 May 2024 09:53:52 +0000 Received: by mail-lj1-x22c.google.com with SMTP id 38308e7fff4ca-2e3efa18e6aso5022331fa.0 for ; Thu, 16 May 2024 02:53:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; t=1715853228; x=1716458028; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=gm/UmOvYzr4EcsRjdOmtcWsiGc6xH0iJcEw/uiql3BE=; b=QGsSsLzimwL+T/alQZWCNfp/ec1052aLpXQyef1Q91jjeZoGs7XsFUkYVoH8i53w70 09Tx0n5d9bIGIYyazdzYZxR6fI6CrAi0L5sjefWJgxnDndSwzABIqICoMAQ92KSnwPkg M2nIOwtjowAIlruaYxYx1DFYAXQM3T/9EHvIVRzHeRdFoBqVLLRwibmcbqP11HtDt5Gw jjGJK5Vl7pG0BaEZtuLtrhfRll37Wrt2JRdoqvEnNoImpmfcjPedkQN/Gl1/gVQnLGuX a90Smgfh1TtRsnM1ZGBKfTOorB2shi3Gc5BDtQnJWIaTbQSPl9S1NMxEfAddg8j+AQJQ H/cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715853228; x=1716458028; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=gm/UmOvYzr4EcsRjdOmtcWsiGc6xH0iJcEw/uiql3BE=; b=Knt0xeDc+ivFiIuAbgSBzjqCPBdNwucxqb+Yscg6gFoDDp0tQUSDES6GJUq+KXxHUN 6qCJhZa2rVVEQHpvx3+mUdhw0JSwWCPcdX8cXuu9w78uoUlsZrKDkbapazhLpC2zXY/9 kZyK+vJ1OftgpJDjdKg8n76gnCoARjll11wdL7d0BEpwC3kSdRhgawKFwWrB/BDr9vgz hUJEqOC4WYC00e4CyzsdyuJyEvD8LNi4jNxwA/F0soEKQG7ICLv5+UM4Mbkrp2TwYfKp rZx5j6gGdTLtP8bjTwSN58rSG46TmffLrWQnlFtZI4au05Eplr+Da73UZ+4f7OPGrOik //8Q== X-Forwarded-Encrypted: i=1; AJvYcCUvsmKz5DUrCZL3UNGsq+MPHc3imC2VF3jdv3w8Z17QbjZD0XnexRgVudp5ouqr3PedBEGKHOgC6T1Bn+OFzK5raaul0HUF05PrRzSb6Go= X-Gm-Message-State: AOJu0YwCkCPhLeWYQo8kxpzKZGn0pfgVNrku1TUU6fpUN7khxf/pVoPr Ljsi/bd3mZrxNpXa3patD923cQn5mV0opoJd1r87NYD0DNLdMceokWjnOWk+LE3Xf0SBl1AZ2Xk 8m5K4TkapXMUxKopKaLRu3swe+ReRReU9fjqg4Iovls3D9MQ= X-Google-Smtp-Source: AGHT+IFu1Cg+5ui0BNK8GxPqdX7hXa36OixlCuQ3PNQ9MT4jQP+Fn4HBF5gsRIWe8pBdLP8lB/kgEygVVtnsq0rPJJQ= X-Received: by 2002:a2e:2a45:0:b0:2dd:6235:a5ec with SMTP id 38308e7fff4ca-2e51b17fe21mr59769031fa.17.1715853227936; Thu, 16 May 2024 02:53:47 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Thu, 16 May 2024 10:53:36 +0100 Message-ID: Subject: Re: Regarding feature #6841 To: Anil Sahoo Cc: Thom Brown , Aditya Toshniwal , pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000236e9706188f36ef" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000236e9706188f36ef Content-Type: text/plain; charset="UTF-8" On Wed, 15 May 2024 at 12:33, Anil Sahoo wrote: > Hi Team, > > I have implemented the Execute query feature and tested it with different > kinds of test cases. > > FYI the PostgreSQL Do block does not work as a single statement when we > put the cursor inside the block at different positions. > > The cursor position is mentioned using pipe('|') and underlined query is > the active query that will run on click of Execute query button. > > I have attached some screenshots for reference. > > Please let me know if you have any questions. > That is exactly the sort of behaviour I was afraid of :-(. At least we have safeguards in place to minimise the chances of the user running something unexpected. -- Dave Page pgAdmin: https://www.pgadmin.org PostgreSQL: https://www.postgresql.org EDB: https://www.enterprisedb.com --000000000000236e9706188f36ef Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, 15 May 2024 at 12:33, Anil Sa= hoo <anil.sahoo@enterpris= edb.com> wrote:
Hi Team,<= div>
I have implemented the Execute query feature and tested it wit= h different kinds of test cases.

FYI the PostgreSQ= L Do block does not work as a single statement=C2=A0when we put the cursor = inside the block at different positions.=C2=A0

The= cursor position is mentioned using pipe('|') and underlined query = is the active query that will run on click of Execute query button.

I have attached=C2=A0some screenshots for reference.= =C2=A0

Please let me know=C2=A0if you have any que= stions.

That is exactly t= he sort of behaviour I was afraid of :-(. At least we have safeguards in pl= ace to minimise the chances of the user running something unexpected.
=
=C2=A0
--
--000000000000236e9706188f36ef--