From: Tom Lane <tgl@sss.pgh.pa.us>
To: buschmann@nidsa.net
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17924: Inverted behavior of "Date" and "Reverse Date" when
 searching a mailbox archive
In-reply-to: <17924-e2de0e7357152edb@postgresql.org>
References: <17924-e2de0e7357152edb@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sun, 07 May 2023 10:27:27 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4144337.1683468308.1@sss.pgh.pa.us>
Date: Sun, 07 May 2023 10:05:08 -0400
Message-ID: <4144338.1683468308@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/4144338.1683468308%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> When changing the order of the result set from "Rank" to "Reverse Date" I
> observed that "Date" gives the results from newest to oldest while "Reverse
> Date" gives them from oldest to newest.
> This seems to me a mismatch and quite confusing.
> The semantics of Date and Reverse Date should be corrected (exchanged)

It's been like that for a decade or two, and you are the first to
complain AFAIR.  Changing it at this point would doubtless add a
lot more confusion than it subtracts.

We could perhaps change to some other terms entirely, like
"Newest First" and "Oldest First", but I'm not convinced that
that's an improvement either.

			regards, tom lane