Re: [pgsql-advocacy] Oracle buys Innobase - Mailing list pgsql-general

From Dann Corbit
Subject Re: [pgsql-advocacy] Oracle buys Innobase
Date
Msg-id D425483C2C5C9F49B5B7A41F8944154757D203@postal.corporate.connx.com
Whole thread Raw
Responses Re: [pgsql-advocacy] Oracle buys Innobase  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-general
> -----Original Message-----
> From: Stephan Szabo [mailto:sszabo@megazone.bigpanda.com]
> Sent: Wednesday, October 19, 2005 12:39 PM
> To: Dann Corbit
> Cc: Marc G. Fournier; Richard_D_Levine@raytheon.com; pgsql-
> general@postgresql.org
> Subject: Re: [pgsql-advocacy] [GENERAL] Oracle buys Innobase
>
> On Wed, 19 Oct 2005, Dann Corbit wrote:
>
> > Yes, clearly that is the wrong result according to the SQL standard.
> >
> > Here is a SQL*Server query:
> > select 1 where 'a' = 'a ' AND 'a' = 'a  ' AND 'a ' = 'a         '
> >
> > It returns (correctly): 1
>
> Doesn't that depend on the collating sequence in use, or is a NO PAD
> collating sequence not allowed here?

If the implementation defines constants as NO PAD and the implementation
defined pad character is something other than space, then they could
compare unequal.

I would find that implementation disturbing.  But I am easily bent out
of shape.

The attached HTML file in my earlier post is the official quote from the
SQL 99 standard.  That is the formal and correct definition, far
superior to my off the cuff approximations.


pgsql-general by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: [pgsql-advocacy] Oracle buys Innobase
Next
From: "Dann Corbit"
Date:
Subject: Re: [pgsql-advocacy] Oracle buys Innobase