Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pvf7M-0004Vg-Aq for pgsql-bugs@arkaria.postgresql.org; Sun, 07 May 2023 14:12:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pvf7L-00042Q-51 for pgsql-bugs@arkaria.postgresql.org; Sun, 07 May 2023 14:12:03 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pvf7K-0003yD-SF for pgsql-bugs@lists.postgresql.org; Sun, 07 May 2023 14:12:02 +0000 Received: from ma03-relay.lansolnet.com ([176.95.46.36]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pvf7D-0012IN-9u for pgsql-bugs@lists.postgresql.org; Sun, 07 May 2023 14:12:01 +0000 Received: from unknown ([192.168.8.231]) by ma03-relay.lansolnet.com; Sun, 07 May 2023 16:11:51 +0200 Received: from MBX200E.cloud4partner.com (192.168.8.234) by MBX200B.cloud4partner.com (192.168.8.231) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Sun, 7 May 2023 16:11:48 +0200 Received: from MBX200E.cloud4partner.com ([fe80::881b:2a52:f04f:d634]) by MBX200E.cloud4partner.com ([fe80::881b:2a52:f04f:d634%13]) with mapi id 15.01.0669.032; Sun, 7 May 2023 16:11:48 +0200 From: Hans Buschmann To: Tom Lane CC: "pgsql-bugs@lists.postgresql.org" Subject: AW: BUG #17924: Inverted behavior of "Date" and "Reverse Date" when searching a mailbox archive Thread-Topic: BUG #17924: Inverted behavior of "Date" and "Reverse Date" when searching a mailbox archive Thread-Index: AQHZgM6eOAL+gVxeVUyj+SXdfD6UV69OtrcAgAAiNcA= Date: Sun, 7 May 2023 14:11:48 +0000 Message-ID: <0dfc8fde847c49b38f7106bbd3140fd9@nidsa.net> References: <17924-e2de0e7357152edb@postgresql.org>,<4144338.1683468308@sss.pgh.pa.us> In-Reply-To: <4144338.1683468308@sss.pgh.pa.us> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.8.240] Content-Type: multipart/alternative; boundary="_000_0dfc8fde847c49b38f7106bbd3140fd9nidsanet_" MIME-Version: 1.0 X-cloud-security-sender: buschmann@nidsa.net X-cloud-security-recipient: pgsql-bugs@lists.postgresql.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on ma03-relay.lansolnet.com with F0704198389F X-cloud-security-connect: unknown[192.168.8.231], TLS=1, IP=192.168.8.231 X-cloud-security: scantime:.4197 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --_000_0dfc8fde847c49b38f7106bbd3140fd9nidsanet_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello Tom, I don't mind the exact wording, but it should be semantically correct. Order by date is ascending (as in SQL). I would propose to change the wording, perhaps like Newest to oldest (or yo= ur suggestion) and make sure, that the selected order shows up in the resul= ts. It is only part of the WebSite, so I don't fear any automation difficulties= . Hans Buschmann ________________________________ Von: Tom Lane Gesendet: Sonntag, 7. Mai 2023 16:05 An: Hans Buschmann Cc: pgsql-bugs@lists.postgresql.org Betreff: Re: BUG #17924: Inverted behavior of "Date" and "Reverse Date" whe= n searching a mailbox archive PG Bug reporting form 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 "Rever= se > 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 --_000_0dfc8fde847c49b38f7106bbd3140fd9nidsanet_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello Tom,


I don't mind the exact wording, but it should be semantically correct.


Order by date is ascending (as in SQL).


I would propose to change the wording, perhaps like Newest to oldest (or= your suggestion) and make sure, that the selected order shows up in the re= sults.


It is only part of the WebSite, so I don't fear any automation difficult= ies.


Hans Buschmann



Von: Tom Lane <tgl@sss= .pgh.pa.us>
Gesendet: Sonntag, 7. Mai 2023 16:05
An: Hans Buschmann
Cc: pgsql-bugs@lists.postgresql.org
Betreff: Re: BUG #17924: Inverted behavior of "Date" and &= quot;Reverse Date" when searching a mailbox archive
 
PG Bug reporting form <noreply@postgresql.org&g= t; writes:
> When changing the order of the result set from "Rank" to &qu= ot;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 convince= d that
that's an improvement either.

            &nb= sp;           regards, to= m lane
--_000_0dfc8fde847c49b38f7106bbd3140fd9nidsanet_--