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 1s9kR4-004rRI-UC for pgsql-admin@arkaria.postgresql.org; Wed, 22 May 2024 11:47:12 +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 1s9kR4-00GHCC-NB for pgsql-admin@arkaria.postgresql.org; Wed, 22 May 2024 11:47:10 +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 1s9kR4-00GHC4-Bf for pgsql-admin@lists.postgresql.org; Wed, 22 May 2024 11:47:10 +0000 Received: from mail-yw1-x1132.google.com ([2607:f8b0:4864:20::1132]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s9kR0-001Reu-T1 for pgsql-admin@lists.postgresql.org; Wed, 22 May 2024 11:47:09 +0000 Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-61df496df01so5876417b3.3 for ; Wed, 22 May 2024 04:47:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716378426; x=1716983226; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=x1tEk9VXEzva4/yDdHarydHxn/1fnBTUqsIfGgzl1xw=; b=JaLpeOgRj2JQmGjJ5JRquPye8pzsAkDi+hrt2RZWPfdJ3VcM54Vr+Ru+WTns+3vlKE cAxqiCECyBek4c6hFozep0vxI7bYN8k22+lLj+DjoXsRqelOTRroh16uBfouEtbuwZ8f xGmmr5p8c8snuPti0K30YOd/F0tiggsX3b+focuw87tONdUD963xHoQ4HR+fXjfqWgna xuMWmiWXeFbWQJZtvGYLQm/BCr+nKkhaZyS/hN44ZI57G9EfoQj+Wy1wMp/k5yR/Vge+ kQClXmqLZiNYRvnqxcWkeJk3IsJscygiWM7kaSg6OdEs94kVnwA8FzjBPb0En7TKlh/J 7bIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716378426; x=1716983226; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=x1tEk9VXEzva4/yDdHarydHxn/1fnBTUqsIfGgzl1xw=; b=iUbKpp4TnoIXHvyxoex2uKV5LC814Rx/rXPzSjAkTfqTjCDgORvl9OJpi+oH+6sY6q Shjr5HnyamR/n0yWrJoxcCYeIRICrgmPdM7YUFZKHfcnqph4msYI5i+Lq1pi1g/CiDcZ AA1d8FBzxV43TCZBopIBZpINLWlgeCzcoJYaRvDkyALJd9NCSD1b7hbCHbgmQ+J2zThm crK6Aup39mX4lJ90pfFBej8PMLauCu+WuWJ0JcX3c9cAWfuE3BQbRHKU4XGdyVt+6I5G TvVeixZOYfoyDLmR3eCwfRvFPIhBtOt5BwhaT/4rKCAVnfz/7c6O4ia9Xpm3M1WQUoZy A0sQ== X-Gm-Message-State: AOJu0YyxdEKdWu77gxPdOaIsxL9SkA2k6Tnmu3VkKb+OvZYWoiqRic71 IO1ltf21PKascrZLRxHd5qwJZMaQEc7Y9dyvjMT5DYJGXkcZCwx7d91C6lyk58cgQZ8DPrgo+DU U8re5TbThik8OBNbw97b2+Q5OZPF2Osw3 X-Google-Smtp-Source: AGHT+IGC0iw72QyowY+Ry1IhyI57pJZgYLgHt/U0w3n4ZIolV8OxalMEEanySdHa9bnVcZhCYOL2gJ20BLpchN67zZM= X-Received: by 2002:a0d:d9c5:0:b0:627:5e68:69e6 with SMTP id 00721157ae682-627e467d6c2mr15984387b3.11.1716378426036; Wed, 22 May 2024 04:47:06 -0700 (PDT) MIME-Version: 1.0 From: Luke Campbell Date: Wed, 22 May 2024 21:46:53 +1000 Message-ID: Subject: displaying line breaks / increasing row height in pgadmin To: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000625a300619097ee7" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000625a300619097ee7 Content-Type: text/plain; charset="UTF-8" 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, --000000000000625a300619097ee7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi pgadmin maillist,

Is ther= e 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 t= o 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 st= rings to display as paragraphs or otherwise indicate that there's more = than what's displayed.

Yours,
--000000000000625a300619097ee7--