[postgis-devel] [PostGIS] #1345: ST_StartPoint, ST_EndPoint regress failure

[PostGIS]

#1345: ST_StartPoint, ST_EndPoint regress failure
-----------------------+----------------------------------------------------
  Reporter:  robe      |       Owner:  pramsey      
      Type:  defect    |      Status:  closed       
  Priority:  critical  |   Milestone:  PostGIS 2.0.0
 Component:  postgis   |     Version:  trunk        
Resolution:  fixed     |    Keywords:               
-----------------------+----------------------------------------------------

Comment(by robe):

 Hmm looking at SQL Server, IBM docs, and ESRI docs, I'm tempted to say
 that even though this is a breaking change we should document it as such
 and perhaps even go so far as to throw an error if handed a multipolygon.
 My dirty self says make it the way it was, but the purist Leo coughing
 down my throat says short-lived pain must be endured for long-lived
 purity.

 http://msdn.microsoft.com/en-us/library/bb933845%28v=sql.100%29.aspx

 http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/opt/rsbp4098.htm

 http://webhelp.esri.com/arcgisserver/9.3/java/index.htm#geodatabases/st_numinteriorring.htm

 It seems we are the only ones who think this is okay to use with
 multipolygons,

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/1345#comment:11>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.