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 1sOCYA-00CyhK-PL for pgadmin-hackers@arkaria.postgresql.org; Mon, 01 Jul 2024 08:38:14 +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 1sOCY9-00H6cP-4z for pgadmin-hackers@arkaria.postgresql.org; Mon, 01 Jul 2024 08:38:13 +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 1sNHf9-006Zov-A6; Fri, 28 Jun 2024 19:53:39 +0000 Received: from mail-pg1-x52d.google.com ([2607:f8b0:4864:20::52d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sNHf6-003bHf-Ay; Fri, 28 Jun 2024 19:53:38 +0000 Received: by mail-pg1-x52d.google.com with SMTP id 41be03b00d2f7-6eab07ae82bso710055a12.3; Fri, 28 Jun 2024 12:53:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719604414; x=1720209214; 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=z+D6OCgO38NxL4POz1WQepDjrMqoqhfzfcrKHO8IWGM=; b=KREROQV1h5WEdZyl3BNnT2vcK7opBVgn3/CQffvZzyi6ox84MA9D08TgwTL9G8zWmK QkYxOCpYnS2T3M/hVuZtEKQ9WXQP7EBz5ONiRhvyOxtF2gmyEI8JrrTtpcDfOC3EF0Zv YKrBPTnKRxxH3TLCAvJfmOFLkjIw6JrbjsOrsJM+jjAKtc7gYc7jJ5KWQD3L5CQApmQq t4dsHUwkx/tarhLBWFl43KukWGq2p6lioghdkee1xH4GXf/fj+9yI3Rzq8oAlij9Cjoq IxkubUVCPtt8m+IStlP4ThhtqyOre1rOLB9iKZF9jEQ6ayMo1NQuOcitg+Ebv/sSqEEQ XSPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719604414; x=1720209214; 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=z+D6OCgO38NxL4POz1WQepDjrMqoqhfzfcrKHO8IWGM=; b=EM2kzifqKXZpuSWHKk5MC5ZOi1V55vyzbqNDZU7rI+7F1XGyrOOMqW+Bf3WMZjAVuV kaYEDvurAD3wHfa+SH6lI5C7XOqMDft429n18yhuRDL0WmlRG2Nz0Z7gUn99vSXnzC/f OUpo65qn5JyMnsqIGJ0bj64pwK6OlVq+6SIcRmb+Yw6HWQZt8berFopoCGpwnP45PxHI eqcyO1adnGZCETOFrOry8e9pI022X1DgnS6TeiTmdSpdkwqR/M0vKD5cqEb5+CB6MC2/ zWuQGT9/aZh6JsJ4E0E8eqrhQFBy14bO0NJEu6y6pPRH/zycKOjgYuDRR7IVS/ZAKkt8 L1yA== X-Forwarded-Encrypted: i=1; AJvYcCW0y/XeCPh77AvjOEYuoHMn5EA8z4YOnwdL9oYpRFuPUk6Knq7J8Ixzbw93dcf3WMyrTn1Up/fmuKWSmekZNtb7So/ygJPHgfL+xxWgXrU= X-Gm-Message-State: AOJu0YwzpA0y4367Diq+1qNbS9gUmker5MHH23VmWn/kEOEGH8L211PP TBCUJ+BwQaSTcwcuMpQ6GXwOSN5kNQMRqz7XbbQyDGRw4N+ytoDlkY5RpVbuVdvfLvKFtXkpBNx DeQZckfycBraVlSgbIVBrmC44yw8= X-Google-Smtp-Source: AGHT+IFnpTYhIqPdE6qjeB/SjJ/Nbts/cPcgfbJrHghEXT/SgANG47uyS4e7w7/lnyqgkFMR+UYZ338dkTvg/ASHoow= X-Received: by 2002:a05:6a21:6d9e:b0:1be:ec6d:9d64 with SMTP id adf61e73a8af0-1beec6df271mr1773573637.21.1719604414073; Fri, 28 Jun 2024 12:53:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Usman Khan Date: Sat, 29 Jun 2024 00:53:22 +0500 Message-ID: Subject: Re: Query tool data grid - Infinite scroll vs Pagination To: Aditya Toshniwal Cc: pgAdmin Support , pgadmin-hackers , Dave Page Content-Type: multipart/alternative; boundary="00000000000041526b061bf89a76" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000041526b061bf89a76 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Aditya I vote for pagination, it would really be helpful for end users. In addition to giving the user the ability to set page size, if he can also select or enter what page he can jump to say 501, 990 etc it would be helpful. On Fri, Jun 28, 2024 at 3:44=E2=80=AFPM Aditya Toshniwal < aditya.toshniwal@enterprisedb.com> wrote: > 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/1FAIpQLSdfJhNK8qXSe9mKcubZa8jjjYl0hiZV= xhv6GGJo8WJcYc27ug/viewform?usp=3Dsharing >> >> On Thu, Jun 20, 2024 at 1:36=E2=80=AFPM Dave Page wr= ote: >> >>> 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 scr= olls >>>> 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 >>>> it 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. O= ne >>>> 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 improvemen= t. >>>> 4. Predictable UI, no jumping scrollbars. >>>> >>>> Let me know what you think. >>>> >>> >>> >>> I think there are definite benefits, but there is the downside of havin= g >>> to scroll and click to browse results. Personally I'm fine with that, b= ut I >>> think you should probably poll pgadmin-support for opinions from more u= sers. >>> >>> -- >>> 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" >> > > > -- > Thanks, > Aditya Toshniwal > pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com* > > "Don't Complain about Heat, Plant a TREE" > --00000000000041526b061bf89a76 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Aditya
I vote for pagination, it would really be he= lpful for end users.
In addition to giving the user the ability t= o set page size, if he can also select or enter what page he can jump to sa= y 501, 990 etc it would be helpful.=C2=A0

On Fri, Jun 28, 2024 at = 3:44=E2=80=AFPM Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> wrote:
Hi,

<= div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif">Unfort= unately, 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> wrot= e:
H= i Everyone,

Request you to share your opinion on this and respond on:<= /div>
= https:= //docs.google.com/forms/d/e/1FAIpQLSdfJhNK8qXSe9mKcubZa8jjjYl0hiZVxhv6GGJo8= WJcYc27ug/viewform?usp=3Dsharing

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, A= ditya Toshniwal <aditya.toshniwal@enterprisedb.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">
Hi Hackers,

Query tool data grid currently pulls the data on load basis in batche= s. For example, it will initially load only 1000 rows and once a user scrol= ls to the 1000th row, it will fetch the next batch of 1000.
Many users who want access in between r= ows 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 UX and= the scrollbar may jump. One reported here -=C2=A0https://github.com= /pgadmin-org/pgadmin4/issues/1780
One more aspect to this is the in memory data of the que= ry tool which keep on increasing on each scroll, it affects the performance= .

I propose we should use pagination inst= ead 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=C2=A0y= ou think.


I think there are definite benefits, but there is the downside of hav= ing to scroll and click to browse results. Personally I'm fine with tha= t, but I think you should probably poll pgadmin-support for opinions from m= ore 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