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 1rm4eh-005rCx-Df for pgadmin-hackers@arkaria.postgresql.org; Mon, 18 Mar 2024 04:31:24 +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 1rm4eg-00FCsR-1K for pgadmin-hackers@arkaria.postgresql.org; Mon, 18 Mar 2024 04:31:22 +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 1rm4ef-00FCsJ-QY for pgadmin-hackers@lists.postgresql.org; Mon, 18 Mar 2024 04:31:22 +0000 Received: from mail-oo1-xc2b.google.com ([2607:f8b0:4864:20::c2b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rm4eb-0054rM-Ko for pgadmin-hackers@postgresql.org; Mon, 18 Mar 2024 04:31:20 +0000 Received: by mail-oo1-xc2b.google.com with SMTP id 006d021491bc7-5a47a9f7755so1489912eaf.0 for ; Sun, 17 Mar 2024 21:31:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1710736278; x=1711341078; 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=lDTwgfm9ocXggxW89l7pFyDpMxLkJOMFlo9MnFADvhw=; b=M0ke+A0hR6woSL0cb8VOanc1YcPwouBmcy/k2SpW0ZOwmwjcxrqWUspvE+68eRAx9A o8cD2B5I1k06ij2VWI5S50Lr2s97qy+BciBCvHRMLnb3qMCiOQNIWeaheGgTHYndyB1m ChlQJFA2wSloNs05pkX729Sf0W11ffw2sFjxMKzE8PDzrk78+C+EbEo9gjafsSX6bIrl S8dnRWP25hBqUU+djQ5c8QnurXXIAQXXvUBA/WyTayyvuaBlZThvo0XXZvTUggqR0yW+ HRAKWmTc/O99kJKFImMfPitytu+C4JMeatrlTsxJ88GrCffizw8komLD+FfSEkcUoCCj czKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710736278; x=1711341078; 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=lDTwgfm9ocXggxW89l7pFyDpMxLkJOMFlo9MnFADvhw=; b=cJYVdWzx0AjGBwaCYUhX5raKY1f9Sc3jGLYbHj03fFy5gUWNqL+Sq2nemhgTrZv6Tw YID3bqbw1SmIpV0en1J00L3Ut/X+UbHnU4NrOdJ7U2N4sUnKurmv3nsn8Vh5oSGMiEWR eKNfPbQMU87nyTO0IS0M+49DdJ0yoFNCjJtENQt+BNInj83jrgKSkW+VqXky5all6FvJ nEtsVekk8tvBpl06fbATbscYzPq4TrklQ/6PETG3MCD9tFvEntJ5bpZ902F4hltPCbHM NlQ0MdV7cnPGv5Hpz/puhThZuGAIjd4VBRk1PPjS6NywF1ZtAhyXA/ALh7+6mMLY/K+6 2nfw== X-Gm-Message-State: AOJu0YzZqOu7epIr5THDRPTNMdago1F2/EBZdC2dbdM5Hz6cYU60xKbQ XID+0tDcDCgAjcciNS/MTtJYASAl1+aNsjKBpYwmC7vMD18EZEWKbhsOhFcFwT/KkOgnMcCtdL6 KkG1mcu9Ijfqy87jte6KiUSTWIo4MscQqA2J7 X-Google-Smtp-Source: AGHT+IGMU1abBlkNygVxbr9Wzr2WVVwpS9LtOzxIikPITZdD9aQ9hmaKwUulu2ZmnZbDVT5z5q+HStqWPOAv/vhHCJc= X-Received: by 2002:a05:6820:20f:b0:5a4:93b6:9a5 with SMTP id bw15-20020a056820020f00b005a493b609a5mr3296732oob.4.1710736277814; Sun, 17 Mar 2024 21:31:17 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Aditya Toshniwal Date: Mon, 18 Mar 2024 10:00:42 +0530 Message-ID: Subject: Re: Enhancement Request - Query Tool - Run non-contiguous highlighted code To: Christopher Maurer Cc: pgadmin-hackers@postgresql.org Content-Type: multipart/alternative; boundary="00000000000024dc480613e7d476" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000024dc480613e7d476 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Christopher, Can you please report this here - https://github.com/pgadmin-org/pgadmin4/issues/new? Additionally, please also add some screenshots or screen recording to help us understand the issue better. On Sun, Mar 17, 2024 at 10:12=E2=80=AFPM Christopher Maurer wrote: > PGADMIN4's Query Tool will run only the highlighted SQL when a section of > the SQL window is highlighted. In the Windows operating system, this sam= e > window allows the highlighting of non-contiguous areas using > ctrl-click&drag on the mouse, but executing such multi-region highlighted > code fails because only the bottom-most highlighted region is executed. > > Note that this could be VERY useful when you have coded a CTE (common > table expression), as this code is at the top of the SQL and > its utilization may occur significantly below its definition. > --=20 Thanks, Aditya Toshniwal pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com* "Don't Complain about Heat, Plant a TREE" --00000000000024dc480613e7d476 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Christopher,

Can you please report this here -=C2= =A0https://g= ithub.com/pgadmin-org/pgadmin4/issues/new? Additionally, please also ad= d some screenshots or screen recording to help us understand=C2=A0the issue= better.

On Sun, Mar 17, 2024 at 10:12=E2=80=AFPM Christopher Maurer= <chrismaurer52@gmail.com= > wrote:
PGADMIN4's Query Tool will run only the highlighted SQL wh= en a section of the SQL window is highlighted.=C2=A0 In the Windows operati= ng system, this same window allows the highlighting of non-contiguous areas= using ctrl-click&drag=C2=A0on the mouse, but executing such multi-regi= on highlighted code fails because only the bottom-most highlighted region i= s executed.

Note that this could be VERY useful when you= have coded a CTE (common table expression), as this code is at the top of = the SQL and its=C2=A0utilization may occur significantly below its definiti= on.


--
Thanks,
Aditya Toshniwal
pgAdmin Hacker=C2=A0| Sr. Software Architect=C2=A0| enterprisedb.com