From: | Thomas Good <tomg(at)sqlclinic(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Chad Thompson <chad(at)weblinkservices(dot)com>, Postgres SQL List <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Concatenation Snafu |
Date: | 2003-03-25 23:47:56 |
Message-ID: | Pine.LNX.4.44.0303251842550.24922-100000@q8.nrnet.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Tue, 25 Mar 2003, Tom Lane wrote:
> "Chad Thompson" <chad(at)weblinkservices(dot)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.
I'd prefer we matched Oracle syntax whenever possible. Then again I
don't like typing all that much. ;-)
> 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.
You are correct. I checked it again: I must have tripped over this
before as the datatypes on one system (7.3.1) don't match the other
(7.3.2) in essentially the same table.
-----------------------------------------------------------------------
Thomas Good e-mail: tomg(at)sqlclinic(dot)net
Programmer/Analyst phone: (+1) 718.818.5528
Residential Services fax: (+1) 718.818.5056
Behavioral Health Services, SVCMC-NY mobile: (+1) 917.282.7359
// Krieg ist selbst Terror - Fr Frieden und globale Gerechtigkeit!
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2003-03-26 04:43:56 | Re: Does anyone use TO_CHAR(INTERVAL)? |
Previous Message | Tom Lane | 2003-03-25 23:34:45 | Re: Concatenation Snafu |