From: | Troels Arvin <troels(at)arvin(dot)dk> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [BUGS] 7.4: CHAR padding inconsistency |
Date: | 2003-11-20 19:14:11 |
Message-ID: | pan.2003.11.20.19.14.11.147818@arvin.dk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Thu, 20 Nov 2003 12:40:30 -0500, Tom Lane wrote:
> AFAICS the Oracle and SQL Server behaviors are at least as inconsistent
> as our own.
> If trailing spaces are significant during concatenation,
> why aren't they significant to LENGTH()?
Oracle _does_ count the trailing spaces in it's LENGTH()-function. MSSQL's
rules certainly look strange.
> I'd agree with changing bpcharlen() to not count trailing spaces,
> I think. That would be consistent with ignoring them in other contexts.
Why not just change the behaviour back to what it used to be like? I see
no justification for the change: It may break old queries in subtle ways
and doesn't make the CHAR-type any more consistent than before.
--
Greetings from Troels Arvin, Copenhagen, Denmark
From | Date | Subject | |
---|---|---|---|
Next Message | Troels Arvin | 2003-11-20 19:16:44 | Re: 7.4: CHAR padding inconsistency |
Previous Message | Tom Lane | 2003-11-20 17:40:30 | Re: [BUGS] 7.4: CHAR padding inconsistency |
From | Date | Subject | |
---|---|---|---|
Next Message | Kurt Roeckx | 2003-11-20 19:14:35 | 7.4 logging bug. |
Previous Message | Chester Kustarz | 2003-11-20 18:48:21 | Re: [HACKERS] More detail on settings for pgavd? |