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 > -----Original Message----- > From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general- > owner@xxxxxxxxxxxxxx] On Behalf Of Marc G. Fournier > Sent: Wednesday, October 19, 2005 11:41 AM > To: Richard_D_Levine@xxxxxxxxxxxx > Cc: pgsql-general@xxxxxxxxxxxxxx > Subject: Re: [pgsql-advocacy] Oracle buys Innobase > > On Wed, 19 Oct 2005, Richard_D_Levine@xxxxxxxxxxxx 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) > > ---- > Marc G. Fournier Hub.Org Networking Services > (http://www.hub.org) > Email: scrappy@xxxxxxx Yahoo!: yscrappy ICQ: > 7615664 > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
