From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | andrew(at)supernews(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: @ versus ~, redux |
Date: | 2006-09-06 01:24:58 |
Message-ID: | 1157505898.20589.61.camel@dogma.v10.wvs |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2006-09-04 at 10:45 -0400, Tom Lane wrote:
> Andrew - Supernews <andrew+nonews(at)supernews(dot)com> writes:
> > On 2006-09-04, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> Do we all agree on this:
> >>
> >> "x @> y" means "x contains y"
> >> "x @< y" means "x is contained in y"
>
> The existing geometric containment tests seem to be nonstrict, so if we
> wanted to leave room to add strict ones later, it might be best to
> settle on
>
> x @>= y x contains or equals y
> x <=@ y x is contained in or equals y
>
> reserving @> and <@ for future strict comparison operators.
>
At first glace, it seems more intuitive to me to do:
x @>= y x contains or equals y
x =<@ y y is contained in or equals y
It seems more natural to me because the operators are symmetrical. Am I
missing the mnemonic value of your form?
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-06 03:00:10 | Re: @ versus ~, redux |
Previous Message | Jeremy Drake | 2006-09-06 01:06:11 | Re: [HACKERS] large object regression tests |