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 17:08:57 |
Message-ID: | 1157562537.20589.108.camel@dogma.v10.wvs |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2006-09-05 at 23:00 -0400, Tom Lane wrote:
> Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> > On Mon, 2006-09-04 at 10:45 -0400, Tom Lane wrote:
> >> 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
>
> Hm, I've never seen anyone spell "less than or equal to" as "=<",
> so I'm not sure where you derive "=<@" from? Not saying "no", but
> the other seems clearer to me.
Initially it seemed strange to me because the @ switches sides but the
operator is not symmetrical.
I see what you mean. Standard <= and >= syntax, with an @ on the side of
the container. Now I'll be able to remember it at least, so I'm really
fine with anything.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | ohp | 2006-09-06 17:12:40 | Re: wartho failing |
Previous Message | Andrew Sullivan | 2006-09-06 17:02:43 | Re: Getting a move on for 8.2 beta |