Marcus Andree S. Magalhaes wrote:
> Dear all,
> While checking the last Beta3-Beta4 Changelog of Postgres 8.0,
> I saw the following:
> * doc/TODO: Remove completed items:
> * -Make LENGTH() of
> CHAR() not count trailing spaces
> If I understand correctly, this will lead to the following situation:
> CHAR_LENGTH('ABCD') == CHAR_LENGTH('ABCD ') == 4
> This will definitely break some of our applications.
> Just want to be sure if this LENGTH() behaviour _will_ appear
> on the next version of Postgres. If true, can we somehow revert
> to the current LENGTH() behaviour?
> Can someone, please, clarify this issue?
You should review the release notes. The full description is:
* Make length() disregard trailing spaces in CHAR(n) (Gavin)
This change was made to improve consistency: trailing spaces
are semantically insignificant in CHAR(n) data, so
they should not be counted by length().
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
In response to
pgsql-novice by date
|Next:||From: Tom Lane||Date: 2004-10-29 22:31:50|
|Subject: Re: behaviour of LENGTH() in postgresql v. 8 |
|Previous:||From: Marcus Andree S. Magalhaes||Date: 2004-10-29 22:10:47|
|Subject: behaviour of LENGTH() in postgresql v. 8|