Re: behaviour of LENGTH() in postgresql v. 8

From: "Marcus Andree S(dot) Magalhaes" <marcus(dot)magalhaes(at)vlinfo(dot)com(dot)br>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Marcus Andree S(dot) Magalhaes" <marcus(dot)magalhaes(at)vlinfo(dot)com(dot)br>, pgsql-novice(at)postgresql(dot)org
Subject: Re: behaviour of LENGTH() in postgresql v. 8
Date: 2004-10-29 22:41:12
Message-ID: 53800.201.12.65.196.1099089672.squirrel@201.12.65.196
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Thanks for your answer. We're already using text and varchar, so we
should be safe when we migrate our server.

<snip>
> If you think trailing spaces are semantically significant, you should be
> using varchar or text fields to store them. In CHAR(n) fields they are
> not significant, and we're doing our best to make that interpretation
> consistent across all operations.
<snip>

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Terry Lee Tucker 2004-10-30 01:08:38 Array Question
Previous Message Tom Lane 2004-10-29 22:31:50 Re: behaviour of LENGTH() in postgresql v. 8