Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 7A379474E49 for ; Tue, 26 Feb 2002 00:10:40 -0500 (EST) 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 g1Q5AiS27480; Tue, 26 Feb 2002 00:10:44 -0500 (EST) To: "Josh Berkus" Cc: pgsql-sql@postgresql.org Subject: Re: Timestamp operator error In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Mon, 25 Feb 2002 21:03:39 -0800" Date: Tue, 26 Feb 2002 00:10:44 -0500 Message-ID: <27477.1014700244@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200202/380 X-Sequence-Number: 6802 "Josh Berkus" writes: > Is there a way, for example, that I could disallow the TIMESTAMP --> > DATE implicit conversion in my code? 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. My approach would be to rename rather than delete the pg_proc entry (say update "date" to "datexxx" in proname); then you could reverse the rename after finding your problems. On the other hand, if you're doing the testing in a deletable temporary database, this isn't a problem. regards, tom lane