From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: sort order of messages |
Date: | 2013-01-14 20:46:47 |
Message-ID: | CABUevEw-tHy7qweGGj6j_SBmy-QAri7wthEb=GPeZBbga3PcUw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Mon, Jan 14, 2013 at 9:27 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> On Mon, Jan 14, 2013 at 9:16 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Well, First/Last would be nice, but if you just add them at the bottom
>>> of the page they will not help all that much --- it's the scroll-down
>>> requirement that I'm mainly whining about. Could we have at least a
>>> subset of these at the top of the page?
>
>> Sure, that shouldn't be too hard. We could repeate the
>> First|Prev|Next|last, or we could repeat the whole thing including the
>> month links easy enough.
>
> First|Prev|Next|last would be enough for me, though maybe others have
> other opinions.
I've put the Prev/Next and month links there for now.
Figuring out the First and Last links actually requires some more
thinking (surprising as that might sounds..), so I'll do that later.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-01-14 20:56:06 | Re: sort order of messages |
Previous Message | Tom Lane | 2013-01-14 20:27:00 | Re: sort order of messages |