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 1sAkmH-00C59c-Oa for pgadmin-hackers@arkaria.postgresql.org; Sat, 25 May 2024 06:21:15 +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 1sAkmG-00CsCV-2y for pgadmin-hackers@arkaria.postgresql.org; Sat, 25 May 2024 06:21:12 +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 1sAkmF-00Cs8B-O4 for pgadmin-hackers@lists.postgresql.org; Sat, 25 May 2024 06:21:11 +0000 Received: from mail-oi1-x234.google.com ([2607:f8b0:4864:20::234]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sAkm9-001tEK-O7 for pgadmin-hackers@lists.postgresql.org; Sat, 25 May 2024 06:21:10 +0000 Received: by mail-oi1-x234.google.com with SMTP id 5614622812f47-3d1b7ad2283so588261b6e.3 for ; Fri, 24 May 2024 23:21:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716618065; x=1717222865; 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=aC+WUSMPT5/RJesDqRAL2zYh0QuY3Qjaaye19A+l3wo=; b=LjS1KF8wZ+PxMuuIXPWKMbGShB61M4wqY2W2ymiH458uQVU0CwQUzp7Ca1ETww1LVK l9yPDfEifo7//+lawWNKIl3/2uCOdzfUJSlWUo22Ox9jiRpZRDeqMufuZ9skQyjl0v/m ziHk25TecyUHmwCyTfvR+b+fO9/UXxApx447KY+XrCxNi1snj49oqQUfRW8zzl0B1OpD p2yOnCMHibfuwoyB2oo2ApXXG6OMdWFjJ+heShL1vHSksdhbO+icJuNciMqFiLbf2a1j uNSNptZuN7qzCyBDhmY9BCWSrLJUSOp97u2CJZDruhAnE4Jb/zZ3GECRznXGkSIam135 Y3NQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716618065; x=1717222865; 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=aC+WUSMPT5/RJesDqRAL2zYh0QuY3Qjaaye19A+l3wo=; b=YqRBNzASN5IHy3R4/Y6CIO7iXMyK0epPx4h2dRBUF8FtRKvgRj8YVptln5TRsTC+Oh jt1MpoYApx2FzLQUM/+u+VrSiYIIhPbBYk1MKjWp8X5mfyyPrOMc1hFoD6bMbpqgG0KL qTjfrrQ6GlEDmScUnMK4z/RyhMX9+Nrc/pg9L21jS4Ewq5QzPuNKPkQgf6SGYBHhknOx dUq8hlOHTGOMyt+Jb8AVIS/x3go8iReAW+H651nAbBJR38IrB7Xj9rG0DnsRiV7oEUG1 hmL5254Q0/UkFhUlIE6AvIe/i3ZeFHn3vYZod/3kRMcmQ1qyUvqqBRfDREsEyhsXZCrv z7bw== X-Gm-Message-State: AOJu0Yy3b71cLnQ8U2Tjmt2QANOzIWVx44/2UsQhgT5OMA4grf8WIGzB 1svoBEBVS9vtWo6p2WU619z3S8nJGpEQD04w109XPuzruuCRy+l3V3sU+4+C1vvczpS0pXWxks0 Gld0S1T8chSG5gY4n2Tqeyjoli9Q= X-Google-Smtp-Source: AGHT+IFqGvmVYg3BTpcOGYmaj3zsxBih6X0XtaiERPmu63E4P2AjKGhkYm05BwcEUxBPkQzXa3WKdD8M6Aezr9+/FQM= X-Received: by 2002:a05:6808:ec7:b0:3c6:12fa:286 with SMTP id 5614622812f47-3d1a5953562mr4982659b6e.15.1716618064762; Fri, 24 May 2024 23:21:04 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Usman Khan Date: Sat, 25 May 2024 11:20:55 +0500 Message-ID: Subject: Re: displaying line breaks / increasing row height in pgadmin To: Luke Campbell Cc: pgadmin-hackers@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000f7200206194149f1" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f7200206194149f1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, There seems no automatic way to achieve this in pgadmin 4 yet. To cater the situation so that you do not miss any such output and get an immediate clue that particular column or cell contain carriage return we can tweak with the query a little like following (which replaces carriage return with '\n') SELECT REPLACE(your_column, E'\n', '\n') AS formatted_text FROM your_table; Additionally, any questions related to pgadmin 4 can directly be asked at 'pgadmin-hackers' for quick response. Note: Removing psql-hackers and adding pgadmin-hackers in the mail list. On Wed, May 22, 2024 at 4:47=E2=80=AFPM 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, > --000000000000f7200206194149f1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
There seems no automatic way to achieve= this in pgadmin 4 yet.

To cater the situation so = that you do not miss any such output and get an immediate clue that particu= lar column or cell contain carriage return we can tweak with the query a li= ttle like following (which replaces carriage return with '\n')
<= /div>

SELECT REPLACE(your_column, E'\n', '\n= ') AS formatted_text
FROM your_table;

Addit= ionally, any questions related to pgadmin 4 can directly be asked at 'p= gadmin-hackers' for quick response.

Note: Remo= ving psql-hackers and adding pgadmin-hackers in the mail list.

On = Wed, May 22, 2024 at 4:47=E2=80=AFPM Luke Campbell <lukejcampbell7@gmail.com> = 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 displa= y line breaks / carriage returns by default, but this has caused me to inco= rrectly 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 wha= t's displayed.

Yours,
--000000000000f7200206194149f1--