From: | Dave Page <dave(dot)page(at)enterprisedb(dot)com> |
---|---|
To: | navnath gadakh <navnath(dot)gadakh(at)enterprisedb(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: [pgAdmin][RM5157] Default sort order at start in view table data by primary key by default |
Date: | 2020-04-16 11:30:46 |
Message-ID: | CA+OCxoybvpAorf3dCbUYXnLADvk+WVts1DxVaOmQyNEdRugG=w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Thu, Apr 16, 2020 at 12:08 PM navnath gadakh <
navnath(dot)gadakh(at)enterprisedb(dot)com> wrote:
> Hi Dave/Team,
> This patch is related to the default sort order for the view
> table data. In pgAdminIII default ordering is by primary key and this is
> not working in pgAdminIV.
> I have attached the patch with the back end code.
>
> Please review it.
>
> *Question*: There is one suggestion on
> https://redmine.postgresql.org/issues/5157 about to put a checkbox in the
> configuration for this behavior.
> Do I need to implement that really? I yes, Is
> preferences a good place for that? / Suggestions?
>
I think we should make this optional, and yes, Preferences is a good place.
The reason is that sorting data is not without cost - at the very least it
will require use of an index to access what may be the whole table.
--
Dave Page
VP & Chief Architect, Database Infrastructure
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
From | Date | Subject | |
---|---|---|---|
Next Message | Murtuza Zabuawala | 2020-04-16 11:52:44 | [pgAdmin4][RM#3495] Do not check for binary content if BOM marker is present in the file |
Previous Message | Khushboo Vashi | 2020-04-16 11:26:23 | Re: [pgAdmin][RM5157] Default sort order at start in view table data by primary key by default |