From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Matt Janssen <matt(at)luggagepros(dot)com> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: FW: UI Addition Request. View Data > View BOTTOM 100 Rows |
Date: | 2010-08-13 00:07:15 |
Message-ID: | AANLkTiktUOyOmUk5Kr7+mun_LL1a+V+4aeq9FtmogBQe@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Thu, Aug 12, 2010 at 11:08 PM, Matt Janssen <matt(at)luggagepros(dot)com> wrote:
>>"Top" just means the first 100 returned by an unordered select query.
>>They're actually in a completely arbitrary order, as that's how
>>Postgres stores them, so "bottom" doesn't really make any sense. We
>>don't make any attempt to order, as we have no idea what makes sense
>>for any particular table - you can specify your own ordering in the
>>filter/sort dialog of course.
>
> Not to argue since I'm pretty novice with pgAdmin, but every time I open a
> table with "View Top 100 Rows" the filter/sort options are already set to
> PRIMARY KEY Ascending. Can we offer the reverse behavior?
Hmm, that must have been snuck in when I wasn't looking :-p
I guess we could offer that in reverse.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | pgAdmin Trac | 2010-08-13 05:35:19 | [pgAdmin III] #223: PgAdmin Crash |
Previous Message | Matt Janssen | 2010-08-12 22:08:18 | FW: UI Addition Request. View Data > View BOTTOM 100 Rows |