Bug #477: path ?# path - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Bug #477: path ?# path
Date
Msg-id 200110091917.f99JH9N64033@postgresql.org
Whole thread Raw
Responses Re: Bug #477: path ?# path  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Bug #477: path ?# path  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Curtis Barrett (curtis@northwestern.edu) reports a bug with a severity of 3
The lower the number the more severe it is.

Short Description
path ?# path

Long Description
nothing major. the ?# (geometric intersection) operator for paths iterates over point pairs in each path testing for
intersection.however, it ignores the last->first point pair for closed paths. a quick workaround is to tack the first
pointon the end of a closed path. 

Sample Code
# select '((1,1),(2,0))'::path ?# '((0,0),(0,2),(2,2))'::path;
 ?column?
----------
 f
(1 row)

# select '((1,1),(2,0))'::path ?# '((0,0),(0,2),(2,2),(0,0))'::path;
 ?column?
----------
 t
(1 row)


No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug #476: pg_dump error: dtoi4: integer out of range
Next
From: Mika Mantyla
Date:
Subject: SQLPutData bug ?