Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 702DB474E49 for ; Tue, 26 Feb 2002 00:03:36 -0500 (EST) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.2) with HTTP id 810156; Mon, 25 Feb 2002 21:03:39 -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:03:39 -0800 Message-ID: In-Reply-To: <27308.1014698855@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200202/379 X-Sequence-Number: 6801 Tom, > Emergency fix? This operator didn't behave reasonably in 7.1 either > (at least not by my definition of reasonable). What exactly would > you have us do? No, not you! For me to fix. You're a volunteer, as far as I'm involved. I just wanted suggestions for a quick fix. When I found the other issues, it was more reasonable to search-and-replace on values ("interval"() for interval() was easy). I can't figure out how to pattern match on interval + timestamp, especially with variables involved. Is there a way, for example, that I could disallow the TIMESTAMP --> DATE implicit conversion in my code? That would break all the functions and views with this problem, and then I could identify them. > Yah. Offhand I'd argue that no information-discarding conversion > should be implicitly invokable. date->timestamp is fine; > timestamp->date should require an explicit cast. I've already > proposed > that we add a flag to pg_proc to distinguish implicit from explicit > conversion operations, and no one complained. But we have not yet > begun to argue about exactly which conversions should be allowed > implicitly... Hey, feel free to take up the argument here, too! It is a SQL topic, after all ... -Josh ______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