Re: No commit nor Rollback button

On Tue, Oct 17, 2017 at 1:07 AM, Dave Page wrote: > I can see why for some people who choose to turn auto-commit/auto-rollback > off they may be useful, however we cannot simply add new features every > time someone asks for something. Doing so adds maintenance costs, and >

Re: Data grid: fetching/scrolling data on user demand

On Tue, Oct 17, 2017 at 1:44 PM, Tomek wrote: > Hi, > > It is not exactly truth... In v3 the query is executed, fetched and > all rows are displayed, > >>> > >>> No they're not, though they are all transferred to the client which is > why it's slower. > >> > >> They are

Re: Data grid: fetching/scrolling data on user demand

On Tue, Oct 17, 2017 at 11:35 AM, Tomek wrote: > Hi, > > >> It is not exactly truth... In v3 the query is executed, fetched and all > rows are displayed, > > > > No they're not, though they are all transferred to the client which is > why it's slower. > > They are not what?

Faded text in pgAdmin 4 2.0/Win Server 2008r2

Must be something wrong in my setup: Windows Server 2008 r2 TS, acessing with two Full HD 24" monitors in 32bit color depth., themes disabled, font smoothing enabled, composition enabled, visual effects disabled. I just can't read texts... They are "faded". See attached screenshot for

Re: Data grid: fetching/scrolling data on user demand

Hi, >> It is not exactly truth... In v3 the query is executed, fetched and all rows >> are displayed, > > No they're not, though they are all transferred to the client which is why > it's slower. They are not what? What is slower - is the "display" part in both versions. You have data from

Re: Data grid: fetching/scrolling data on user demand

Hi Tomek, On Tue, Oct 17, 2017 at 3:21 PM, Tomek wrote: > Hi, > > > As I mentioned in my previous email that we do not use server side > cursor, so it won't add any > > limit on query. > > > > The delay is from database driver itself, it has nothing to do with > pgAdmin4. >

Re: Data grid: fetching/scrolling data on user demand

On Tue, Oct 17, 2017 at 10:51 AM, Tomek wrote: > Hi, > > > As I mentioned in my previous email that we do not use server side > cursor, so it won't add any > > limit on query. > > > > The delay is from database driver itself, it has nothing to do with > pgAdmin4. > > Try

Re: Data grid: fetching/scrolling data on user demand

Hi, > As I mentioned in my previous email that we do not use server side cursor, so > it won't add any > limit on query. > > The delay is from database driver itself, it has nothing to do with pgAdmin4. > Try executing the same query in 'psql', 'pgAdmin3' and third party tool which > use libpq

Re: Data grid: fetching/scrolling data on user demand

On Tue, Oct 17, 2017 at 9:36 AM, legrand legrand < legrand_legr...@hotmail.com> wrote: > Pgadmin doesn't have to Wait for all the data, > As he should only load/fetch the first 1000 rows. > > Loading all the data in memory will not be possible for big datasets. > > This is a design error at my

Re: Data grid: fetching/scrolling data on user demand

Pgadmin doesn't have to Wait for all the data, As he should only load/fetch the first 1000 rows. Loading all the data in memory will not be possible for big datasets. This is a design error at my point of view. PAscal SQLeo projection manager -- Sent from:

Re: Data grid: fetching/scrolling data on user demand

On Tue, Oct 17, 2017 at 6:36 AM, Murtuza Zabuawala < murtuza.zabuaw...@enterprisedb.com> wrote: > > On Tue, Oct 17, 2017 at 2:22 AM, legrand legrand < > legrand_legr...@hotmail.com> wrote: > >> How long does it take in your environnment >> to fetch the 1000 first records from >> >> select * from

Re: No commit nor Rollback button

On Tue, Oct 17, 2017 at 6:26 AM, Murtuza Zabuawala < murtuza.zabuaw...@enterprisedb.com> wrote: > > On Tue, Oct 17, 2017 at 2:03 AM, legrand legrand < > legrand_legr...@hotmail.com> wrote: > >> Hi Murtuza, >> >> I found those options for switching between autocommit mode and manual >> mode. >> >>