[postgis-devel] Issue 66 in postgis: ST_Dump kills backend when fed CIRCULAR STRING

[codesite-noreply at google.com]

Issue 66: ST_Dump kills backend when fed CIRCULAR STRING
http://code.google.com/p/postgis/issues/detail?id=66

Comment #6 by robe.... at cityofboston.gov:
Mark,

I took a quick glance at the Dump code in lwgeom_dump.c.  The first glaring  
problem I
see is that it assumes that all geometry types (from 4 on ) #define	 
MULTIPOINTTYPE	4
are multis or collections.  All the curved types are in the 8+ range.  So I  
am
guessing it is trying to break up a circular string which can't be broken  
up and runs
into a fault as as result.  This we should at least change to not hard code  
the
assumption that >= MULTITYPE are MULTIs or collections.  It would be nice  
if we can
come up with a more elegant way of checking this rather than the number  
range which
is prone to change.

Anyrate I'll try to change this to a case range later and see how that  
fairs.  I'm
sure there are more complications further down (the code later on looks a  
bit scarier
to digest).




-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings