From: | pgsql-bugs(at)postgresql(dot)org |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Bug #477: path ?# path |
Date: | 2001-10-09 19:17:09 |
Message-ID: | 200110091917.f99JH9N64033@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Curtis Barrett (curtis(at)northwestern(dot)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 point on 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
From | Date | Subject | |
---|---|---|---|
Next Message | MikeSmialek | 2001-10-10 02:09:29 | comment on inheritance |
Previous Message | Tom Lane | 2001-10-09 13:33:20 | Re: Bug #476: pg_dump error: dtoi4: integer out of range |