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 |
Thread: | |
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 | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2009-02-03 11:04:00 | Re: Request for features - filtering options. |
Previous Message | Glyn Astill | 2009-02-03 10:54:26 | Re: Request for features - filtering options. |