From: | "Guy Rouillier" <guyr(at)masergy(dot)com> |
---|---|
To: | "PostgreSQL General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Handling of pad characters (was RE: Oracle buys Innobase ) |
Date: | 2005-10-21 19:51:50 |
Message-ID: | CC1CF380F4D70844B01D45982E671B239E8BF7@mtxexch01.add0.masergy.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Alex Turner <armtuk(at)gmail(dot)com> writes:
>> It appears that casting to a char() causes spaces to be stripped
>> (ignored) from the string:
> mls=# select length('123 '::char(8));
> length
> --------
> 3
> (1 row)
>
>> I'm not sure about anyone else, but I would personaly consider that a
>> bug?
>
> No, it's a feature, as per extensive discussion some time ago when we
> made it do that. The general rule is that trailing spaces in a
> char(n) are semantically insignificant.
How did you reach the opposite conclusion for varchar? If anything, I
would think that stripping pad characters makes more sense for varchar
than it does for char. But that may simply be bias from experience, as
my first real DBA work was with DB2, where fixed length columns really
are fixed length.
--
Guy Rouillier
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-10-21 20:12:10 | Re: Select all invalid e-mail addresses |
Previous Message | Magnus Hagander | 2005-10-21 19:41:41 | Re: looking for alternative to MySQL's GROUP_CONCAT function |