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 1s9lWM-0050CS-TT for pgsql-admin@arkaria.postgresql.org; Wed, 22 May 2024 12:56:44 +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 1s9lWM-00GwDE-SC for pgsql-admin@arkaria.postgresql.org; Wed, 22 May 2024 12:56:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s9lWM-00GwD4-Gv for pgsql-admin@lists.postgresql.org; Wed, 22 May 2024 12:56:42 +0000 Received: from mail-lf1-x131.google.com ([2a00:1450:4864:20::131]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s9lWI-000Cg1-Ha for pgsql-admin@lists.postgresql.org; Wed, 22 May 2024 12:56:41 +0000 Received: by mail-lf1-x131.google.com with SMTP id 2adb3069b0e04-51f1e8eaee5so682939e87.1 for ; Wed, 22 May 2024 05:56:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bitnine-net.20230601.gappssmtp.com; s=20230601; t=1716382597; x=1716987397; darn=lists.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=P4aL3+JTdYYeEqu4llP0h3rqlRjyBOWopSwoSw2MQME=; b=GNC/bhu/iGcDkHCD1kT8wiV9cIbZAzpjSXn2A/0fC6IEmFvGR1FwbalaEhDserhd+O roz7GO4uJQOhO3TgpanqXf/zngaWJkRfx0zzPEa8SpcIt3qXisJj/NffZVsCrGsAXhQE E1W5lA7Wr8f3nwImq+ui/tKGH7q5GDfDq/gRZVxNgH5Y9TqZH8wwcjUSpwZ1kObuY1J7 F393S8nlWGJoXwqH4+FbWCmRylgp8NS2uCOA0CbGMtA1IwyqbDDH4xV9XnpTkEA23NAy DcIMSXRUvniVlVaG2IzPW4D/qrop5yWepQ7KvAAi5KLEElARQShFof/dRAeb1npQR6nS usBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716382597; x=1716987397; 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=P4aL3+JTdYYeEqu4llP0h3rqlRjyBOWopSwoSw2MQME=; b=gggQ6tx7QDUGxP1rU1Pke1mwQ3dsQqXy206lwcukduMdVDHFEQLNEC5D3pdvsm9hU6 EOWMNQeeXN5VF1A56o+9EGqSeuniOV0ztfWk6Pw4AlRMoodgHUxTWKrtepBP4sD48ula eg5n4GSmHCQppDTn/f+SK+VIvpA9jWWtmVy5nmb0DWFnzy0eL0VCwfTTXH7s0BeEJq5V i/wbSyW4sM4MpsZUt5KeGq2dznWIkdqVl8OWaMd3YvsCo1E3ycTB5GqxpawWfbvRnhXD YKTzMejdWMDNAefMJ7FWXWPXfxaW+C27zf1EHhkpFgfet+Tfl+fIIXTXaNWrUuFL3keD /f5g== X-Gm-Message-State: AOJu0Yy+vyr26adtUAxQAq1h0gWEAsg6lfgOaQKcxvfCwTO8KoF5PKJg 9H2FY+Rz1J3Ueb2VEVYAWcqbpRug61xA4Dvj6zNYhAOpWkw4kVwL1tK8sNbB7iUWHreJA8c4SWa Gh8NcBBGXo0q8FgTluJ9HFZT7DmOONnhkA0+NY9wlmaY1Jw1Yb35PTg== X-Google-Smtp-Source: AGHT+IFQHAxr5E0BCveSEBH5VHVwWfO6uNFIuLh7ajp0bYS/Fp8qPi/GzHBvixsmqGcMcrPtyXO7A2vtRQjtM81HZAE= X-Received: by 2002:a19:a418:0:b0:522:2a1b:2c7b with SMTP id 2adb3069b0e04-524079b14e1mr3434496e87.13.1716382597333; Wed, 22 May 2024 05:56:37 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Muhammad Salahuddin Manzoor Date: Wed, 22 May 2024 17:56:26 +0500 Message-ID: Subject: Re: displaying line breaks / increasing row height in pgadmin To: Luke Campbell Cc: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000035ee906190a77e7" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000035ee906190a77e7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dear Luke, In pgAdmin 4, as of version 8.6, there is no direct setting to automatically adjust the row height in the results grid to fit multiline strings. However, you can use the following workarounds to better manage the display of multiline text in your results grid. Use the Cell Edit Panel: Enable Word Wrap in the Query Tool: Adjust Row Height Manually: Custom Query Formatting: External Tools: *Salahuddin (=EC=82=B4=EB=9D=BC=ED=9B=84=EB=94=98**)* On Wed, 22 May 2024 at 16:47, Luke Campbell wrote: > Hi pgadmin maillist, > > Is there a way to make the results grid in pgadmin automatically increase > rows' height if a string contains a carriage return? > > I've updated pgadmin 4 to 8.6 and strings in the results grid now seem to > display line breaks / carriage returns by default, but this has caused me > to incorrectly think that was the end of the string. I would like these > strings to display as paragraphs or otherwise indicate that there's more > than what's displayed. > > Yours, > --000000000000035ee906190a77e7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear Luke,

In pgAdmin 4, as of version = 8.6, there is no direct setting to automatically adjust the row height in t= he results grid to fit multiline strings. However, you can use the followin= g workarounds to better manage the display of multiline text in your result= s grid.

Use the Cell Edit Panel:
Enable Word Wrap in the Query To= ol:
Adjust Row Height Manually:
Custom Query Formatting:
External = Tools:

Salahuddin (=EC=82=B4=EB=9D=BC=ED=9B=84=EB=94=98)<= /b>



On Wed, 22 May= 2024 at 16:47, Luke Campbell <lukejcampbell7@gmail.com> wrote:
Hi pgadmin maillist,
=

Is there a way to make the results grid in pgadmin auto= matically increase rows' height if a string contains a carriage return?=

I've updated pgadmin 4 to 8.6 and strings in = the results grid now seem to display line breaks / carriage returns by defa= ult, but this has caused me to incorrectly think that was the end of the st= ring. I would like these strings to display as paragraphs or otherwise indi= cate that there's more than what's displayed.

Yours,
--000000000000035ee906190a77e7--