Re: [BUGS] 7.4: CHAR padding inconsistency
От | Troels Arvin |
---|---|
Тема | Re: [BUGS] 7.4: CHAR padding inconsistency |
Дата | |
Msg-id | pan.2003.11.20.19.14.11.147818@arvin.dk обсуждение исходный текст |
Ответ на | Re: [BUGS] 7.4: CHAR padding inconsistency (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: [BUGS] 7.4: CHAR padding inconsistency
|
Список | 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
В списке pgsql-hackers по дате отправления: