Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250])
	by postgresql.org (Postfix) with ESMTP id 6129B47595B
	for <pgsql-sql@postgresql.org>; Wed, 10 Jul 2002 15:32:36 -0400 (EDT)
Received: from [66.219.92.2] (HELO chocolate-mousse)
	by davinci.ethosmedia.com (CommuniGate Pro SMTP 3.5.9)
	with ESMTP id 1572612 for pgsql-sql@postgresql.org;
	Wed, 10 Jul 2002 12:32:35 -0700
Content-Type: text/plain;
  charset="us-ascii"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: pgsql-sql@postgresql.org
Subject: BETWEEN bug?
Date: Wed, 10 Jul 2002 12:35:53 -0700
X-Mailer: KMail [version 1.4]
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200207101235.53848.josh@agliodbs.com>
X-Archive-Number: 200207/143
X-Sequence-Number: 8522

Folks,

Why does BETWEEN only work for ascending criteria?  For example:

jwnet=3D> select '2002-06-07'::TIMESTAMP BETWEEN '2002-06-29'::TIMESTAMP an=
d=20
'2002-06-01'::TIMESTAMP;
 ?column?
----------
 f
(1 row)

jwnet=3D> select '2002-06-07'::TIMESTAMP BETWEEN '2002-06-01'::TIMESTAMP an=
d=20
'2002-06-29'::TIMESTAMP;
 ?column?
----------
 t
(1 row)

The above behaviour does not seem logical; is this a SQL spec thing, or a b=
ug?

--=20
-Josh Berkus