Re: Fixing row comparison semantics - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Fixing row comparison semantics
Date
Msg-id BAY20-F8D907221DC981584E2FA7F9340@phx.gbl
Whole thread Raw
In response to Re: Fixing row comparison semantics  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>
>Huh?  The only "current behavior" with other operators is failure:

you didn't understand me. I know so operator <* isn't supported now.
I prefere SQL spec behave too. But what I wont:

a <* b   ~ ai <= bi and one ai < bi => true ; if one ai > bi => NULL; else 
false

but this behave is from some views really chaotic. This comparation is used 
in operation research, but propably is far to ideas ANSI SQL. It was  only 
idea.

>
>regression=# select (1,1) <* (1,2);
>ERROR:  operator <* is not supported for row expressions
>
>In any case, you can get the equivalent of the current behavior by
>writing out
>    1 <* 1 AND 1 <* 2
>so I don't see any strong need to support non-SQL-spec behaviors here.
>
>            regards, tom lane

_________________________________________________________________
Najdete si svou lasku a nove pratele na Match.com. http://www.msn.cz/



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [PATCHES] default resource limits
Next
From: Heikki Linnakangas
Date:
Subject: Re: [DOCS] Online backup vs Continuous backup