Re: @ versus ~, redux

Поиск
Список
Период
Сортировка
Искать
От
Andrew - Supernews
Тема
Re: @ versus ~, redux
Дата
Msg-id
slrnefnmt3.2ea3.andrew+nonews@atlantis.supernews.net
Список
Дерево обсуждения
Re: @ versus ~, redux Andrew - Supernews <andrew+nonews@supernews.com>
Re: @ versus ~, redux Tom Lane <tgl@sss.pgh.pa.us>
Re: @ versus ~, redux Jeff Davis <pgsql@j-davis.com>
Re: @ versus ~, redux Tom Lane <tgl@sss.pgh.pa.us>
Re: @ versus ~, redux Jeff Davis <pgsql@j-davis.com>
Re: @ versus ~, redux "Zeugswetter Andreas DCP SD" <ZeugswetterA@spardat.at>
Re: @ versus ~, redux Bruce Momjian <bruce@momjian.us>
Re: @ versus ~, redux Tom Lane <tgl@sss.pgh.pa.us>
Re: @ versus ~, redux Matteo Beccati <php@beccati.com>
Re: @ versus ~, redux Michael Glaesemann <grzm@seespotcode.net>
Re: @ versus ~, redux Tom Lane <tgl@sss.pgh.pa.us>
On 2006-09-04, Tom Lane  wrote:
> 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"

While I suggested something like those, I would also suggest that the
existing operators for inet/cidr be taken into consideration:
 x >>= y  "x contains y" x >> y   "x strictly contains y" x <<= y  "x is contained in y" x << y   "x is strictly contained in y"

(obviously these don't all necessarily make sense for all types)

These have the advantage of resembling set notation more closely and being
in use in one existing core type.

-- 
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services

В списке pgsql-hackers по дате отправления
От: Dave Page
Дата:
Сообщение: Re: gBorg status?
От: Matteo Beccati
Дата:
Сообщение: Re: @ versus ~, redux
FAQ