Re: @ versus ~, redux - Mailing list pgsql-hackers

From Matteo Beccati
Subject Re: @ versus ~, redux
Date
Msg-id 44FBDB6F.90206@beccati.com
Whole thread Raw
In response to Re: @ versus ~, redux  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: @ versus ~, redux  (Gregory Stark <stark@enterprisedb.com>)
Re: @ versus ~, redux  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane ha scritto:
> OK, so if everyone is leaning to #3, the name game remains to be played.
> Do we all agree on this:
> 
>     "x @> y" means "x contains y"
>     "x @< y" means "x is contained in y"
> 
> Are we all prepared to sign a solemn oath to commit hara-kiri if we
> invent a new datatype that gets this wrong?  No?  Maybe these still
> aren't obvious enough.

Does this mean that also contrib/ltree operators will likely change for 
consistency?

ltree @> ltree    - returns TRUE if left argument is an ancestor of right argument 
(or equal).
ltree <@ ltree    - returns TRUE if left argument is a descendant of right argument 
(or equal).


Best regards
--
Matteo Beccati
http://phpadsnew.com
http://phppgads.com


pgsql-hackers by date:

Previous
From: Andrew - Supernews
Date:
Subject: Re: @ versus ~, redux
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Optimizing prepared statements