Oh that’s great news, thanks so much!
John From: Dave Page <dp...@pgadmin.org> Date: Tuesday, July 18, 2017 at 11:44 PM To: John Payne <jcpa...@uw.edu> Cc: pgAdmin Support <pgadmin-supp...@postgresql.org> Subject: Re: Scrolling vs. pagination The screenshots need updating. Iirc, we got rid of pagination before we released v1.0. The query tool is fully scrolled and much faster than pgAdmin 3 for large result sets now. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK:http://www.enterprisedb.com The Enterprise PostgreSQL Company On 18 Jul 2017, at 22:56, J Payne <jcpa...@uw.edu> wrote: I haven’t used pgAdmin 4 in quite some time, but I checked out the web page today and I see from the screenshots that the output is still paginated for simple queries (like “SELECT * FROM mytable”). For me, that is a deal breaker. Although pgAdmin3 certainly has issues, being able to effortlessly scroll through a long list is still far, far better than any sort of pagination could ever be. Although scrolling can be avoided by writing detailed queries, scrolling is extremely useful for flicking through a table to get a feeling for what’s in it, how many missing values there are, and to catch bad entries (especially if you have no idea what the bad variants might be). It’s even useful with giant tables of hundreds of thousands or millions of rows: although no-one would want to scroll through every row, it still gives you a nearly-instant snapshot. I assume that there are others, perhaps many, who feel as I do, and I beg the pgAdmin4 team to consider making query output a single-page scrolling list. More august personalities than I am have commented on why scrolling should be preferred to pagination. Here is Mike Bostock of D3 fame, for example: https://bost.ocks.org/mike/scroll/. Thanks, John
