Fwd: "Fetching all records..."

From: "microsys(dot)gr microsys(dot)gr" <microsys(dot)gr(at)gmail(dot)com>
To: pgadmin-hackers(at)postgresql(dot)org
Subject: Fwd: "Fetching all records..."
Date: 2018-01-23 11:14:05
Message-ID: CALewnqQC3-ophkFfx2iN7Qb6Ev+BdS90TtGEMtFU+zwdLvyjeg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers pgadmin-support

---------- Forwarded message ----------
From: microsys.gr microsys.gr <microsys(dot)gr(at)gmail(dot)com>
Date: 2018-01-23 13:13 GMT+02:00
Subject: Re: "Fetching all records..."
To: Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com>

Latest version 2.1 installed
Same bug behaviour there, NOTHING CHANGED

2018-01-22 6:32 GMT+02:00 Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com>:

>
> On Fri, Jan 19, 2018 at 8:19 PM, microsys.gr microsys.gr <
> microsys(dot)gr(at)gmail(dot)com> wrote:
>
>> Version 2.0
>> Copyright Copyright 2013 - 2017, The pgAdmin Development
>> Team
>> Python Version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015, 20:32:19)
>> [MSC v.1500 32 bit (Intel)]
>> Flask Version 0.11.1
>> Application Mode Desktop
>> Current User pgadmin4(at)pgadmin(dot)org
>>
>> When open form for the first time or re-run from 'Execute/Refresh(F5)'
>> button everything looks fine.
>> Same good result when run SELECT script.
>>
>> My table shows:
>> Messages
>> Successfully run. Total query runtime: 5 secs.
>> 210930 rows affected.
>>
>> (Table's record size appx. 2700 bytes)
>>
>> - When clicking on the leftmost header cell (Image Region 1) crashes on
>> trying "Fetching all records"
>> - When clicking on any header cell for the first time (Image Region 2),
>> the behaviour is like clicking on the leftmost header cell (Image Region
>> 1), fetching all records before selecting the whole row.
>>
>> The bug is in the onclick event code of the grid header.
>> It seems that when click the header, the SELECT script is re-executed
>> with bug behaviour.
>>
>>
>>
> Logged the bug. Please track with https://redmine.postgresql.org
> /issues/3035
> One suggestion, please upgrade your pgAdmin 4, the latest version is 2.1.
>
> Always keep pgadmin-hackers(at)postgresql(dot)org in loop while reporting a bug.
>
>>
>> 2018-01-19 8:02 GMT+02:00 Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com
>> >:
>>
>>> Hi,
>>>
>>> Please log your bug at https://redmine.postgresql.org/projects/pgadmin4
>>>
>>> Provide pgAdmin 4 version and screen shot of the bug , to understand the
>>> issue easily.
>>>
>>> Thanks,
>>> Khushboo
>>>
>>> On Thu, Jan 18, 2018 at 8:44 PM, microsys.gr microsys.gr <
>>> microsys(dot)gr(at)gmail(dot)com> wrote:
>>>
>>>> OS Windows 10 64-bit
>>>> Python Version 2.7.11
>>>> Flask Version 0.11.1
>>>> Application Mode Desktop
>>>> ---------------------------------
>>>>
>>>> 1. View/Edit Data -> All Rows
>>>> Speed is almost perfect - Well done.
>>>>
>>>> Bug:
>>>> When clicking on top-left corner of grid to fetch all records,
>>>> on large tables pgAdmin4 crashes on "Fetching all records..." screen.
>>>>
>>>>
>>>>
>>>
>>
>

In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2018-01-23 11:22:36 Re: Module-wise Keyboard preferences
Previous Message Dave Page 2018-01-23 11:11:00 Re: [pgadmin4][Patch]: Display Functions node for GreenPlum database

Browse pgadmin-support by date

  From Date Subject
Next Message microsys.gr microsys.gr 2018-01-23 13:40:05 Table Properties... > [Columns tab] very slow
Previous Message McDonaldR 2018-01-23 10:08:16 RE: No notification/progress window under Windows 10