| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | josh(at)agliodbs(dot)com, pgsql-bugs(at)postgresql(dot)org, glenniii(at)mail(dot)utexas(dot)edu |
| Subject: | Re: Bug in concat operator for Char? -- More Info |
| Date: | 2004-07-21 15:00:50 |
| Message-ID: | 20040721075621.T61440@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 21 Jul 2004, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
> > Are these changes intentional,
>
> Yes. We've been moving more and more steadily towards the notion that
> trailing spaces in char(n) values are insignificant noise. If you think
> that trailing spaces are significant, you shouldn't be using char(n)
> to store them.
Well, the problem here is that technically we're returning the wrong type.
We should be returning a char(l1+l2) rather than a text for a char
concatenate, but similarly to the recent complaint about numerics, we
don't really have a fully proper way to do that and it seems non-trivial.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-07-21 15:22:26 | Re: Bug in concat operator for Char? -- More Info |
| Previous Message | Jean-Luc Lachance | 2004-07-21 12:38:02 | Re: Bug in concat operator for Char? -- More Info |