From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Timestamp operator error
Date: Tue, 26 Feb 2002 00:10:44 -0500
Message-ID: <27477.1014700244@sss.pgh.pa.us> (raw)
In-Reply-To: <web-810156@davinci.ethosmedia.com>
References: <web-810156@davinci.ethosmedia.com>
"Josh Berkus" <josh@agliodbs.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com
Subject: Re: Timestamp operator error
In-Reply-To: <27477.1014700244@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox