From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pogden@claresco.com
Cc: pgsql-sql@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Inconsistent or incomplete behavior obverse in where
Date: Tue, 12 Nov 2002 13:44:49 -0500
Message-ID: <10374.1037126689@sss.pgh.pa.us> (raw)
In-Reply-To: <web-1822721@davinci.ethosmedia.com>
References: <web-1822721@davinci.ethosmedia.com>
"Josh Berkus" <josh@agliodbs.com> writes:
> Now, that's interesting. Why would defining a "numeric = float" have
> broken "numeric = integer"? There's no reason I can think of.
The problem probably is that the parser now finds two possible
interpretations that look equally good to it, so it can't choose.
It could coerce the integer constant to numeric (and use numeric=numeric)
or to float (and use the added numeric=float operator), and there's no
rule that can break the tie.
In 7.3 and 7.4 we are actually going in the direction of removing
cross-data-type operators, not adding them, because they tend to create
too many options for the parser to choose from.
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, pogden@claresco.com, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Inconsistent or incomplete behavior obverse in where
In-Reply-To: <10374.1037126689@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