Re: Request for features - filtering options.

Lists: pgadmin-support
From: Marcin <marlag(at)fr(dot)pl>
To: pgadmin-support(at)postgresql(dot)org
Subject: Request for features - filtering options.
Date: 2009-02-03 10:36:09
Message-ID: 1233657369.49881e19c85e3@poczta.fr.pl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgadmin-support

Hello,

I am not a subscriber of mailing list so maybe such idea was
already presented.

It would be nice to see (for me) 2 features in pgAdmin:

1. Table -> View data -> new option: View Bottom 100 Rows which would be
useful in case of checking last changes - otherwise I have view to Top 100
and change ordering

2. Additional select box in View Data Options: "History" - after selecting
option remembered text (by table) would be pasted into Filter textarea.
It would be useful for often/similar filtering which are done during
data maintenance :) The best would be saving this history on the disk - to
use in the future.

--
best regards
ml.


From: Dave Page <dpage(at)pgadmin(dot)org>
To: Marcin <marlag(at)fr(dot)pl>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: Request for features - filtering options.
Date: 2009-02-03 10:52:53
Message-ID: 937d27e10902030252u67ec90a8hcb9a635d507eb518@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgadmin-support

On Tue, Feb 3, 2009 at 10:36 AM, Marcin <marlag(at)fr(dot)pl> wrote:
> Hello,
>
> I am not a subscriber of mailing list so maybe such idea was
> already presented.
>
> It would be nice to see (for me) 2 features in pgAdmin:
>
> 1. Table -> View data -> new option: View Bottom 100 Rows which would be
> useful in case of checking last changes - otherwise I have view to Top 100
> and change ordering

The Top 100 option simply shows the first rows in the arbitrary order
that the server reads them. 'Bottom 100' is meaningless without a
defined order which would obviously be table-specific. At best it
would mean 'the last 100 rows read from disk' but to get those, we'd
need to get all the preceding ones first which makes it pointless
limiting the size of the dataset in the first place.

> 2. Additional select box in View Data Options: "History" - after selecting
> option remembered text (by table) would be pasted into Filter textarea.
> It would be useful for often/similar filtering which are done during
> data maintenance :) The best would be saving this history on the disk - to
> use in the future.

Yes - I'd like to add something similar to the query tool.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com


From: Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk>
To: pgadmin-support(at)postgresql(dot)org, Marcin <marlag(at)fr(dot)pl>
Subject: Re: Request for features - filtering options.
Date: 2009-02-03 10:54:26
Message-ID: 728408.54657.qm@web23608.mail.ird.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgadmin-support

--- On Tue, 3/2/09, Marcin <marlag(at)fr(dot)pl> wrote:

> 1. Table -> View data -> new option: View Bottom 100
> Rows which would be
> useful in case of checking last changes - otherwise I have
> view to Top 100
> and change ordering
>

That would be a nice little touch. I do to 100 and reorder all the time.


From: Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk>
To: Marcin <marlag(at)fr(dot)pl>, Dave Page <dpage(at)pgadmin(dot)org>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: Request for features - filtering options.
Date: 2009-02-03 10:59:17
Message-ID: 281529.57355.qm@web23608.mail.ird.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgadmin-support

--- On Tue, 3/2/09, Dave Page <dpage(at)pgadmin(dot)org> wrote:

> > Hello,
> >
> > I am not a subscriber of mailing list so maybe such
> idea was
> > already presented.
> >
> > It would be nice to see (for me) 2 features in
> pgAdmin:
> >
> > 1. Table -> View data -> new option: View
> Bottom 100 Rows which would be
> > useful in case of checking last changes - otherwise I
> have view to Top 100
> > and change ordering
>
> The Top 100 option simply shows the first rows in the
> arbitrary order
> that the server reads them. 'Bottom 100' is
> meaningless without a
> defined order which would obviously be table-specific. At
> best it
> would mean 'the last 100 rows read from disk' but
> to get those, we'd
> need to get all the preceding ones first which makes it
> pointless
> limiting the size of the dataset in the first place.
>

I see. It'd be nice if there could be some sort of option "order top 100 by primary key" - then perhaps would the last 100 be possible?


From: Dave Page <dpage(at)pgadmin(dot)org>
To: glynastill(at)yahoo(dot)co(dot)uk
Cc: Marcin <marlag(at)fr(dot)pl>, pgadmin-support(at)postgresql(dot)org
Subject: Re: Request for features - filtering options.
Date: 2009-02-03 11:04:00
Message-ID: 937d27e10902030304h2a632b66ra6484a7ff43681c7@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgadmin-support

On Tue, Feb 3, 2009 at 10:59 AM, Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk> wrote:
>
> I see. It'd be nice if there could be some sort of option "order top 100 by primary key" - then perhaps would the last 100 be possible?

Probably - not sure how to make it presentable in the menu though :-).
Patches welcome!!

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com