Ian Barwick <barwick@gmx.net> writes:
> On Sunday 12 January 2003 17:55, Bruce Momjian wrote:
>> I can't say "don't use CHAR(n)" because there are valid reasons to use
>> it.
> I think what Tom is saying is "always use VARCHAR(n) unless you know
> for sure CHAR(n) is what you want, because if you slept through that part of
> the SQL course CHAR(n) is not what you might think."
Yes. It is not clear from either the FAQ or the documentation that
CHAR() should not be one's default choice for a character field.
regards, tom lane
