MIME-Version: 1.0
References: 
 <CAM9w-_mJkHpqE2BSdBsLqOVO4ARaWPDXZGYb5Hn3eMh+sDcOrg@mail.gmail.com>
In-Reply-To: 
 <CAM9w-_mJkHpqE2BSdBsLqOVO4ARaWPDXZGYb5Hn3eMh+sDcOrg@mail.gmail.com>
From: Dave Page <dpage@pgadmin.org>
Date: Thu, 20 Jun 2024 09:06:25 +0100
Message-ID: 
 <CA+OCxozbRmSmRytM2_4_gNvbpqrX0fEyfFVzYPVWH8ftxHchrQ@mail.gmail.com>
Subject: Re: Query tool data grid - Infinite scroll vs Pagination
To: Aditya Toshniwal <aditya.toshniwal@enterprisedb.com>
Cc: pgadmin-hackers <pgadmin-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000031d004061b4dcbf4"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BOCxozbRmSmRytM2_4_gNvbpqrX0fEyfFVzYPVWH8ftxHchrQ%40mail.gmail.com>
Precedence: bulk

--00000000000031d004061b4dcbf4
Content-Type: text/plain; charset="UTF-8"

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 scrolls
> 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. One
> 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, but I
think you should probably poll pgadmin-support for opinions from more users.

-- 
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com

--00000000000031d004061b4dcbf4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi</div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r" class=3D"gmail_attr">On Wed, 19 Jun 2024 at 13:42, Aditya Toshniwal &lt;=
<a href=3D"mailto:aditya.toshniwal@enterprisedb.com">aditya.toshniwal@enter=
prisedb.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;=
border-left-color:rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div =
style=3D"font-family:verdana,sans-serif">Hi Hackers,</div><div style=3D"fon=
t-family:verdana,sans-serif"><br></div><div style=3D"font-family:verdana,sa=
ns-serif">Query tool data grid currently pulls the data on load basis in ba=
tches. For example, it will initially load only 1000 rows and once a user s=
crolls to the 1000th row, it will fetch the next batch of 1000.</div><div s=
tyle=3D"font-family:verdana,sans-serif">Many users who want access in betwe=
en 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. One reported here -=C2=A0<a href=3D"https://gi=
thub.com/pgadmin-org/pgadmin4/issues/1780" target=3D"_blank">https://github=
.com/pgadmin-org/pgadmin4/issues/1780</a></div><div><div style=3D"font-fami=
ly:verdana,sans-serif">One more aspect to this is the in memory data of the=
 query tool which keep on increasing on each scroll, it affects the perform=
ance.</div><div style=3D"font-family:verdana,sans-serif"><br></div><div sty=
le=3D"font-family:verdana,sans-serif">I propose we should use pagination in=
stead of infinite scroll with the following advantages:</div><div style=3D"=
font-family:verdana,sans-serif">1. Users can jump to any page they want.</d=
iv><div style=3D"font-family:verdana,sans-serif">2. Users can change the pa=
ge size on the grid directly.</div><div style=3D"font-family:verdana,sans-s=
erif">3. Memory will be used only for visible rows so performance improveme=
nt.</div><div style=3D"font-family:verdana,sans-serif">4. Predictable UI, n=
o jumping scrollbars.</div><div style=3D"font-family:verdana,sans-serif"><b=
r></div><div style=3D"font-family:verdana,sans-serif">Let me know what=C2=
=A0you think.</div></div></div></blockquote></div><div><br></div><div><br><=
/div><div>I think there are definite benefits, but there is the downside of=
 having to scroll and click to browse results. Personally I&#39;m fine with=
 that, but I think you should probably poll pgadmin-support for opinions fr=
om more users.</div><div><br></div><span class=3D"gmail_signature_prefix">-=
- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">Da=
ve Page<div>pgAdmin: <a href=3D"https://www.pgadmin.org" target=3D"_blank">=
https://www.pgadmin.org</a></div><div>PostgreSQL: <a href=3D"https://www.po=
stgresql.org" target=3D"_blank">https://www.postgresql.org</a><br><div>EDB:=
=C2=A0<a href=3D"https://www.enterprisedb.com" target=3D"_blank">https://ww=
w.enterprisedb.com</a></div><div><br></div></div></div></div></div>

--00000000000031d004061b4dcbf4--