| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | David Garamond <lists(at)zara(dot)6(dot)isreserved(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: text + text |
| Date: | 2004-10-08 13:31:31 |
| Message-ID: | 20041008062558.Q69318@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 8 Oct 2004, David Garamond wrote:
> Peter Eisentraut wrote:
> >>What is "text + text" supposed to do right now?
> >
> > Nothing.
>
> Then are these bugs? (7.4.5 and 8.0.0beta1 give same results). Frankly,
> the current behaviour is quite strange to me.
>
> ------------------
> =# select coalesce('1'+'0','NULL');
> a
That isn't text+text. It's "char"+"char". "char" is a rather bizarre type
being partially 1 byte integer and partially 1 character string and it
causes strange behaviors like the above where I believe it's taking the
first bytes of the '1' and '0' and adding them together. I think Tom was
talking about removing the math operators from it so that things like the
above don't happen.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Glaesemann | 2004-10-08 13:33:08 | Re: when to use NULL and when to NOT NULL DEFAULT '' |
| Previous Message | Bruno Wolff III | 2004-10-08 13:27:14 | Re: interesting! a sequence clashes with data already in that table |