Re: BUG #5889: "Intersects" for polygons broken

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Konrad Garus <konrad(dot)garus(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5889: "Intersects" for polygons broken
Date: 2011-03-11 15:20:37
Message-ID: 201103111520.p2BFKbO21332@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Robert Haas wrote:
> On Tue, Mar 8, 2011 at 3:20 PM, Konrad Garus <konrad(dot)garus(at)gmail(dot)com> wrote:
> > http://www.postgresql.org/docs/current/static/functions-geometry.html
> >
> > I wish it explained what arguments each of the operators accepts, and
> > whether any automatic conversions take place (like polygon to box in
> > that 8.3 issue).
> >
> > What happens when I call ?# or ?- on a polygon and point? Two points? Open path?
> >
> > Some of these are obvious, but others not so much.
>
> Hmm, yeah. That looks like it could be improved. It's certainly not
> obvious to me what box * point means, for example, even though the
> description says scaling/rotation.

Would someone who uses these features please post changes and I will see
that get into the docs? Thanks.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2011-03-11 15:32:28 Re: ecpg preprocessor regression in 9.0
Previous Message Merlin Moncure 2011-03-11 15:12:46 Re: BUG #5837: PQstatus() fails to report lost connection