Re: [pgsql-advocacy] Oracle buys Innobase

> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-
> owner(at)postgresql(dot)org] On Behalf Of Doug Quale
> Sent: Wednesday, October 19, 2005 1:10 PM
> To: pgsql-general(at)postgresql(dot)org
> Subject: Re: [pgsql-advocacy] [GENERAL] Oracle buys Innobase
>
> "Marc G. Fournier" <scrappy(at)postgresql(dot)org> writes:
>
> > On Wed, 19 Oct 2005, Richard_D_Levine(at)raytheon(dot)com wrote:
> >
> >> I was referring to trailing blanks, but did not explicitly say it,
> >> though showed it in the examples. I am pretty sure that the SQL
> >> standard says that trailing whitespace is insignificant in string
> >> comparison.
> >
> > Then we are broken too :)
> >
> > # select 'a ' = 'a ';
> > ?column?
> > ----------
> > f
> > (1 row)
>
> # select 'a'::char(8) = 'a '::char(8);
> ?column?
> ----------
> t
> (1 row)
>
> Trailing blanks aren't significant in fixed-length strings, so the
> question is whether Postgresql treats comparison of varchars right.

An additional (equally salient) question is:

Does PostgreSQL treat comparisons of different types of character
strings with different length attributes appropriately (as described in
the standard)?