From: Tom Lane <tgl@sss.pgh.pa.us>
To: Chad Thompson <chad@weblinkservices.com>
Cc: Thomas Good <tomg@sqlclinic.net>
Cc: Postgres SQL List <pgsql-sql@postgresql.org>
Subject: Re: Concatenation Snafu
Date: Tue, 25 Mar 2003 18:34:45 -0500
Message-ID: <1434.1048635285@sss.pgh.pa.us> (raw)
In-Reply-To: <049c01c2f322$69ee2e90$32021aac@chad>
References: <Pine.LNX.4.44.0303251726580.23371-100000@q8.nrnet.org>
<049c01c2f322$69ee2e90$32021aac@chad>
"Chad Thompson" <chad@weblinkservices.com> writes:
> The assumtion that char and varchar can be compared is gone.
The real problem is that we have too dang many || operators; there's
no reason to have char||char, varchar||varchar, *and* text||text.
The parser can't decide which of the first two to prefer, so it
punts. If we got rid of both and left only text||text, all would be
well.
Thomas is wrong to claim that this used to behave differently; all
versions I have handy to test, back to 7.0, give the same error.
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, chad@weblinkservices.com, tomg@sqlclinic.net
Subject: Re: Concatenation Snafu
In-Reply-To: <1434.1048635285@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