Ran across some behavior that seems odd to me:
SELECT ST_AsText(ST_Boundary(geom))
FROM (VALUES ('POLYGON EMPTY'::GEOMETRY),
('MULTIPOLYGON EMPTY'::GEOMETRY),
('LINESTRING EMPTY'::GEOMETRY),
('MULTILINESTRING EMPTY'::GEOMETRY)
) g (geom);
results in:
'
Yes, I could see that as a reasonable interpretation. Just another in
the large collection of corner cases opened up by allowing typed empty
(my fault). The code probably just tests for empty and reflects the
input back in that case.
P.
On Fri, Jan 9, 2015 at 2:26 PM, BladeOfLight16 wrote:
> Ran
On Fri, Jan 9, 2015 at 6:16 PM, Paul Ramsey
wrote:
> Yes, I could see that as a reasonable interpretation. Just another in
> the large collection of corner cases opened up by allowing typed empty
> (my fault). The code probably just tests for empty and reflects the
> input back in that case.
>
J
On Mon, Jan 12, 2015 at 06:29:32PM -0500, BladeOfLight16 wrote:
> On Fri, Jan 9, 2015 at 6:16 PM, Paul Ramsey
> wrote:
>
> > Yes, I could see that as a reasonable interpretation. Just another in
> > the large collection of corner cases opened up by allowing typed empty
> > (my fault). The code pr
