From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | legrand legrand <legrand_legrand(at)hotmail(dot)com> |
Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Data grid: fetching/scrolling data on user demand |
Date: | 2017-10-16 08:02:53 |
Message-ID: | CA+OCxoyn-142DkF0fJ30CdQyp53Lvnkh4Ybp2D_ZHD7YvmSnRw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Sat, Oct 14, 2017 at 8:24 PM, legrand legrand <
legrand_legrand(at)hotmail(dot)com> wrote:
> Hello,
>
> Data grid is populated without any limit by default,
> it could be a problem with very big datasets ...
>
> To avoid this, it is possible to limit the number of rows retrieved,
> but that limit is fixed, even if user tryes to scroll more data ...
>
> Is scrolling data on demand supported ?
>
pgAdmin 4 loads data on demand (i.e. as the user scrolls) already. That's
why it's significantly faster than pgAdmin 3. The batch size can be changed
(from the default 1000) in the application config file by overriding
the ON_DEMAND_RECORD_COUNT option in web/config_local.py in your
installation.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | dangal | 2017-10-16 13:07:46 | Re: No commit nor Rollback button |
Previous Message | Dave Page | 2017-10-16 07:53:39 | Re: No commit nor Rollback button |