Tom Lane wrote:
> Ian Barwick <[EMAIL PROTECTED]> 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.

I think part of our problem is that we say CHAR() first, then VARCHAR(),
in the docs and the FAQ.  This of course suggests to look at CHAR()
first, then VARCHAR(), which is wrong.  I have fixed the FAQ, and now
the SGML docs.  I think this will help.

  Bruce Momjian                        |
  [EMAIL PROTECTED]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to