Skip site navigation (1) Skip section navigation (2)

Re: Bug in concat operator for Char? -- More Info

From: Jean-Luc Lachance <jllachan(at)sympatico(dot)ca>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: josh(at)agliodbs(dot)com, pgsql-bugs(at)postgresql(dot)org,glenniii(at)mail(dot)utexas(dot)edu
Subject: Re: Bug in concat operator for Char? -- More Info
Date: 2004-07-21 12:38:02
Message-ID: 40FE63AA.5020501@sympatico.ca (view raw or flat)
Thread:
Lists: pgsql-bugs
This means that there is no more difference between CHAR(N) and 
VARCHAR(N). To bad... '1 ' sould be different from '1'.


Tom Lane wrote:

> Josh Berkus <josh(at)agliodbs(dot)com> writes:
> 
>>Are these changes intentional,
> 
> 
> Yes.  We've been moving more and more steadily towards the notion that
> trailing spaces in char(n) values are insignificant noise.  If you think
> that trailing spaces are significant, you shouldn't be using char(n)
> to store them.
> 
> 			regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
>                http://archives.postgresql.org
> 


In response to

pgsql-bugs by date

Next:From: Stephan SzaboDate: 2004-07-21 15:00:50
Subject: Re: Bug in concat operator for Char? -- More Info
Previous:From: Junior - CotrijuiDate: 2004-07-21 12:35:27
Subject: Problem: Sequence X Rule Reference!

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group