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 1sN95k-0071nk-Lc for pgadmin-hackers@arkaria.postgresql.org; Fri, 28 Jun 2024 10:44:32 +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 1sN95i-003Ygv-L1 for pgadmin-hackers@arkaria.postgresql.org; Fri, 28 Jun 2024 10:44:30 +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 1sN73r-002cc9-GQ for pgadmin-hackers@lists.postgresql.org; Fri, 28 Jun 2024 08:34:27 +0000 Received: from mail-oo1-xc30.google.com ([2607:f8b0:4864:20::c30]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sN73n-003WFL-GO for pgadmin-hackers@postgresql.org; Fri, 28 Jun 2024 08:34:25 +0000 Received: by mail-oo1-xc30.google.com with SMTP id 006d021491bc7-5c2201ffb1bso147011eaf.2 for ; Fri, 28 Jun 2024 01:34:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1719563662; x=1720168462; 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=aAWTpr/VF8dNqitqS0rkOzlF+VuVVUPE3kh63O+i1Is=; b=hGGRHBJKmRqn6gbEr6pBeUDLpbWw2JcKyn2YhZ+WvLoJELfH0ZYs8sPRu0OS6UeNCJ 5tVPm4voZKW0jToYyVQjtiez1chTo8tIE8FO4LxPK2uQT6kszo/GQ+msVio23KjQZ6p0 X3e+WfEinOEjSvuJfDNJtz6zw4L6EFUryL2wno8FJCIiN+Jr+QCsWL3g72zaxnGuR/6H SGmxcvUuiS7kULJZW4g7GRgmxBBWl6PjkgmN/lo/MV9OoTFj5tDgE//Y5D4XIeWvmbyn zUXQ8uEhKn5mtIcTMu6N13A5WbPXho3HnKmJUWRX657SPiMnSBOmYpMPwukc47pdAKhB J74Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719563662; x=1720168462; 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=aAWTpr/VF8dNqitqS0rkOzlF+VuVVUPE3kh63O+i1Is=; b=WhkACHKOdTK9iDy1HrRZwBD+/unxyBlJuWGzQRDgMr0PaMDgixu2cbzocRYRibNPKL ovnFkimSocgJHZWZeg0WSRla7d1do9htna8YdQxaPhUcpvTTiVMgLO0NrhAEfQYTg472 ZHY0RfAqDoOXzIdVrOI4sqRqz2e94CIMef0EBGQVXCp52xCZXF5hdDVsZZUbwK/GXVPt sf+5vtooPB6o0PgNeM3rd2jPMFxY5/W0ikA2NzHf4Q1OZVRUfn1IT8IwuPTDMx0CqwTs aWYTmkTwFlCWKQdkzdSlBJ7ayzWsrwcGf7jccvoBYKqiKwqbVdU8VE2pTG8pGDoVac3v EX/Q== X-Gm-Message-State: AOJu0Yxv85ZbbTrRf892RUi/KDm66c+rx8unHD7aOI8XPYY4XKgIz0Cl uR5r9h4pS+9W6gl8MbziLqWAFCUgKVRQxjqQKhAIAVhDZfUJrT5x7Nj2HC85pQTvRzYCqSBjggs NOOSh3rA/3FnXixitBw0ZBh6G57MnYWiOhKQ6R1X9iJ5jyZ4= X-Google-Smtp-Source: AGHT+IFu1gljGMO9rFcIsaxEeK9QdCDCYlmj96wpVkLDsERFmzti+/cED5Ba2W3ketosxUsyQXWa3kbaTBHO5yaLonQ= X-Received: by 2002:a4a:92c2:0:b0:5b2:ff69:9814 with SMTP id 006d021491bc7-5c1eebfe628mr15568600eaf.2.1719563662308; Fri, 28 Jun 2024 01:34:22 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Aditya Toshniwal Date: Fri, 28 Jun 2024 14:03:45 +0530 Message-ID: Subject: Re: Query tool data grid - Infinite scroll vs Pagination To: pgAdmin Support Cc: pgadmin-hackers , Dave Page Content-Type: multipart/alternative; boundary="00000000000042d647061bef1dcf" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000042d647061bef1dcf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Unfortunately, there were only 3 responses to this. In that case, we will discuss internally and decide what to do. On Thu, Jun 20, 2024 at 2:46=E2=80=AFPM Aditya Toshniwal < aditya.toshniwal@enterprisedb.com> wrote: > Hi Everyone, > > Request you to share your opinion on this and respond on: > > https://docs.google.com/forms/d/e/1FAIpQLSdfJhNK8qXSe9mKcubZa8jjjYl0hiZVx= hv6GGJo8WJcYc27ug/viewform?usp=3Dsharing > > On Thu, Jun 20, 2024 at 1:36=E2=80=AFPM Dave Page wro= te: > >> Hi >> >> On Wed, 19 Jun 2024 at 13:42, Aditya Toshniwal < >> aditya.toshniwal@enterprisedb.com> wrote: >> >>> Hi Hackers, >>> >>> Query tool data grid currently pulls the data on load basis in batches. >>> For example, it will initially load only 1000 rows and once a user scro= lls >>> to the 1000th row, it will fetch the next batch of 1000. >>> Many users who want access in between rows or last row struggle to do i= t >>> as the user has to scroll and scroll. If someone grabs the scroller and >>> pulls it down still it will be a good UX and the scrollbar may jump. On= e >>> reported here - https://github.com/pgadmin-org/pgadmin4/issues/1780 >>> One more aspect to this is the in memory data of the query tool which >>> keep on increasing on each scroll, it affects the performance. >>> >>> I propose we should use pagination instead of infinite scroll with the >>> following advantages: >>> 1. Users can jump to any page they want. >>> 2. Users can change the page size on the grid directly. >>> 3. Memory will be used only for visible rows so performance improvement= . >>> 4. Predictable UI, no jumping scrollbars. >>> >>> Let me know what you think. >>> >> >> >> I think there are definite benefits, but there is the downside of having >> to scroll and click to browse results. Personally I'm fine with that, bu= t I >> think you should probably poll pgadmin-support for opinions from more us= ers. >> >> -- >> Dave Page >> pgAdmin: https://www.pgadmin.org >> PostgreSQL: https://www.postgresql.org >> EDB: https://www.enterprisedb.com >> >> > > -- > Thanks, > Aditya Toshniwal > pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com* > > "Don't Complain about Heat, Plant a TREE" > --=20 Thanks, Aditya Toshniwal pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com* "Don't Complain about Heat, Plant a TREE" --00000000000042d647061bef1dcf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

Unfortunately, there were only 3 responses to this.
In= that case, we will discuss=C2=A0internally and decide what to do.

On = Thu, Jun 20, 2024 at 2:46=E2=80=AFPM Aditya Toshniwal <aditya.toshniwal@enterprisedb.com&g= t; wrote:

On Thu, Jun 20, 2024 at 1:= 36=E2=80=AFPM Dave Page <dpage@pgadmin.org> wrote:
Hi

On Wed, 19 Jun 2024 at 13:= 42, Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> wrote:
Hi Hackers,

Query tool data grid currently pulls the data on load basis in b= atches. For example, it will initially load only 1000 rows and once a user = scrolls to the 1000th row, it will fetch the next batch of 1000.
Many users who want access in betw= een rows or last row struggle to do it as the user has to scroll and scroll= . If someone grabs the scroller and pulls it down still it will be a good U= X and the scrollbar may jump. One reported here -=C2=A0https://githu= b.com/pgadmin-org/pgadmin4/issues/1780
One more aspect to this is the in memory data of th= e query tool which keep on increasing on each scroll, it affects the perfor= mance.

I propose we should use pagination i= nstead of infinite scroll with the following advantages:
1. Users can jump to any page they want.
2. Users can change the p= age size on the grid directly.
3. Memory will be used only for visible rows so performance improvem= ent.
4. Predictable UI, = no jumping scrollbars.
<= br>
Let me know what=C2= =A0you think.


<= /div>
I think there are definite benefits, but there is the downside of= having to scroll and click to browse results. Personally I'm fine with= that, but I think you should probably poll pgadmin-support for opinions fr= om more users.

-= -


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

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