RES: Query tool data grid - Infinite scroll vs Pagination

😊 Sorry – I’ve never used it as infinite scroll, I always use “limit n” in my queries (where n is tipically 10) just to develop and test my queries, and use for larger datasets some scripting tool (like Go or Python).
I’ve tables with 2 bi rows, and forgetting to use “limit” is deadly slow.
I love the way you guys deal with those improvements, they are always welcome.

Kind regards,

Edson

De: Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com>
Enviada em: sexta-feira, 28 de junho de 2024 13:42
Para: Edson Richter <edsonrichter(at)hotmail(dot)com>
Cc: pgAdmin Support <pgadmin-support(at)postgresql(dot)org>; pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>; Dave Page <dpage(at)pgadmin(dot)org>
Assunto: Re: Query tool data grid - Infinite scroll vs Pagination

Hi Edson,

The current implementation is infinite scroll. We're planning to replace/improve it.

On Fri, Jun 28, 2024 at 6:48 PM Edson Richter <edsonrichter(at)hotmail(dot)com<mailto:edsonrichter(at)hotmail(dot)com>> wrote:
Infinite scroll usually consume a lot of memory, and generate additional overhead in case of copy data, export, etc. In my humble opinion, if anything then paginated would work better without additional memory consumption.
In case of implementing infinite scroll, please give users a option to disable it.

Thanks,

Edson

Obter o Outlook para Android<https://aka.ms/AAb9ysg>
________________________________
From: Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com<mailto:aditya(dot)toshniwal(at)enterprisedb(dot)com>>
Sent: Friday, June 28, 2024 5:33:45 AM
To: pgAdmin Support <pgadmin-support(at)postgresql(dot)org<mailto:pgadmin-support(at)postgresql(dot)org>>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org<mailto:pgadmin-hackers(at)postgresql(dot)org>>; Dave Page <dpage(at)pgadmin(dot)org<mailto:dpage(at)pgadmin(dot)org>>
Subject: Re: Query tool data grid - Infinite scroll vs Pagination

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 PM Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com<mailto:aditya(dot)toshniwal(at)enterprisedb(dot)com>> wrote:
Hi Everyone,

Request you to share your opinion on this and respond on:
https://docs.google.com/forms/d/e/1FAIpQLSdfJhNK8qXSe9mKcubZa8jjjYl0hiZVxhv6GGJo8WJcYc27ug/viewform?usp=sharing

On Thu, Jun 20, 2024 at 1:36 PM Dave Page <dpage(at)pgadmin(dot)org<mailto:dpage(at)pgadmin(dot)org>> wrote:
Hi

On Wed, 19 Jun 2024 at 13:42, Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com<mailto:aditya(dot)toshniwal(at)enterprisedb(dot)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

--
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Sr. Software Architect | enterprisedb.com<https://www.enterprisedb.com/>
"Don't Complain about Heat, Plant a TREE"

--
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Sr. Software Architect | enterprisedb.com<https://www.enterprisedb.com/>
"Don't Complain about Heat, Plant a TREE"

--
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Sr. Software Architect | enterprisedb.com<https://www.enterprisedb.com/>
"Don't Complain about Heat, Plant a TREE"