Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f76Log654161 for ; Mon, 6 Aug 2001 17:50:42 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f76LoKY24765; Mon, 6 Aug 2001 17:50:20 -0400 (EDT) To: "Josh Berkus" cc: Allan Engelhardt , pgsql-sql@postgresql.org Subject: Re: Re: Data type confusion In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Mon, 06 Aug 2001 13:55:43 -0700" Date: Mon, 06 Aug 2001 17:50:20 -0400 Message-ID: <24762.997134620@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200108/70 X-Sequence-Number: 4291 "Josh Berkus" writes: > I don't want to go through a bunch of non-ANSI SQL-compliant conversion > functions to do it. Especially not as this is just what the ANSI SQL > data type and operator specs are designed to support. Curiously enough, ANSI doesn't define an INTERVAL-divided-by-INTERVAL function either. Also, it rather looks like ANSI adopted the position Peter E. expressed: Year-month intervals are mutually comparable only with other year- month intervals. [...] Day-time intervals are mutually comparable only with other day- time intervals. [...] Operations involving items of type datetime require that the date- time items be mutually comparable. Operations involving items of type interval require that the interval items be mutually compara- ble. regards, tom lane