Re: PATCH: improve sorting in the Data Editor

From: Sanket Mehta <sanket(dot)mehta(at)enterprisedb(dot)com>
To: Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>
Cc: "J(dot)F(dot) Oster" <jinfroster(at)mail(dot)ru>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: PATCH: improve sorting in the Data Editor
Date: 2015-08-05 17:20:51
Message-ID: CA+yw=mOtPp3UuOVXf9dWfMPpkVRqYmA79b20rnkj_X-ZvKTLkg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi,

I have reviewed the patch and below is analysis.

- Behaviour of sorting in data editor before applying the patch is as below:

By default table is sorted by PK/OID in ascending order.
when user select any other column to sort the table, that column gets the
second priority for sorting the table like i.e.order by col_pk, col_column1
where col_pk is column having PK and col_column1 is any other ordinary
column.

- below is the behaviour I have found after applying the patch:

By default table is sorted by PK/OID in ascending order.
When user selects any other column default sorting is removed and table is
getting sorted by newly selected column.
But after this if user wants to sort the table by PK or any other column it
will have the same behaviour like it has before applying the patch. i.e.
order by col_column1, col_PK where col_column1 and col_PK are same as
explained above. It will not sort the table by newly selected
column(col_PK) because sorting of older column(col_column1) is still in
effect and has the higher priority.

This will also confuse the user.

So according to me current behaviour of sorting of table data in pgadmin is
acceptable.

Dave,
Do you have any other thoughts on it?

Regards,
Sanket Mehta
Sr Software engineer
Enterprisedb

On Mon, Aug 3, 2015 at 11:07 AM, Sanket Mehta <sanket(dot)mehta(at)enterprisedb(dot)com
> wrote:

> Sure Ashesh.
>
> Regards,
> Sanket Mehta
> Sr Software engineer
> Enterprisedb
>
> On Mon, Aug 3, 2015 at 10:49 AM, Ashesh Vashi <
> ashesh(dot)vashi(at)enterprisedb(dot)com> wrote:
>
>> Sanket,
>>
>> Can you please review it?
>>
>>
>> --
>>
>> Thanks & Regards,
>>
>> Ashesh Vashi
>> EnterpriseDB INDIA: Enterprise PostgreSQL Company
>> <http://www.enterprisedb.com>
>>
>>
>> *http://www.linkedin.com/in/asheshvashi*
>> <http://www.linkedin.com/in/asheshvashi>
>>
>> On Sun, Aug 2, 2015 at 3:49 PM, J.F. Oster <jinfroster(at)mail(dot)ru> wrote:
>>
>>> Hello,
>>>
>>> Here is a small improvement about sorting in the Data editor.
>>>
>>> Problem:
>>> If a table has a PK or OIDs, it gets sorted by PK/OID by default.
>>> When a user wants to sort by any other column, he has first to click
>>> "Remove sort" in the context menu, and only then click "Sort
>>> ascending"(descending) on column of his choice.
>>>
>>> If he doesn't remove the default sort, he will get no effect and
>>> probably be puzzled for the first time until guesses that he makes
>>> ORDER BY column_pk, column_of_choice
>>> which is totally useless.
>>> The need to "Remove sort" each time is annoying.
>>>
>>> Solution:
>>> When a user chooses to sort by some column, we must discard the
>>> default sort order.
>>>
>>> Please see the attached patch.
>>> Thanks.
>>>
>>> --
>>> Best regards,
>>> J.F.
>>>
>>> --
>>> Sent via pgadmin-hackers mailing list (pgadmin-hackers(at)postgresql(dot)org)
>>> To make changes to your subscription:
>>> http://www.postgresql.org/mailpref/pgadmin-hackers
>>>
>>>
>>
>

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message J.F. Oster 2015-08-06 03:26:12 Re: PATCH: improve sorting in the Data Editor
Previous Message Gabriel E. Sánchez Martínez 2015-08-04 18:59:48 Re: Bug? PgAdmin3, SSL certificate connections refused