Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id A3BE3474E49 for ; Tue, 26 Feb 2002 00:19:59 -0500 (EST) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.2) with HTTP id 810172; Mon, 25 Feb 2002 21:20:02 -0800 From: "Josh Berkus" Subject: Re: Timestamp operator error To: Tom Lane , "Josh Berkus" Cc: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.5.2 Date: Mon, 25 Feb 2002 21:20:02 -0800 Message-ID: In-Reply-To: <27477.1014700244@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200202/381 X-Sequence-Number: 6803 Tom, > Well, you could delete the date(timestamp) function from pg_proc. > However, that would prevent getting from timestamp to date even > with an explicit cast --- so you might want to put it back after > you've found all the trouble spots. Hmmmm, no, that won't work, as lots of my functions have explicit casts. Thanks anyway. Hopefully I don't have many more functions where I call INTERVAL + TIMESTAMP; I just looked at several time-sensitve functions and I'm pretty consistent with the other way 'round. FMI, though, how difficult is defining an operator if I paid a C programmer to do it? -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco