From 28e5de6b00961a5dd75dcb3fe32c2b8ce244d786 Mon Sep 17 00:00:00 2001 From: Regina Obe Date: Wed, 21 Dec 2011 13:14:07 +0000 Subject: [PATCH] #1345 write this off as an observed regression difference and document the behavior for those like me who will be adversely impacted and confused by application breakage. git-svn-id: http://svn.osgeo.org/postgis/trunk@8484 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/reference_accessor.xml | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/doc/reference_accessor.xml b/doc/reference_accessor.xml index 47fb09042..bba4c8812 100644 --- a/doc/reference_accessor.xml +++ b/doc/reference_accessor.xml @@ -292,6 +292,11 @@ ST_Dimension &sqlmm_compliant; SQL-MM 3: 7.1.4 &Z_support; + Changed: 2.0.0 no longer works with single geometry multilinestrings. In older + versions of PostGIS -- a single line multilinestring would work happily with this + function and return the start point. In 2.0.0 it just returns NULL like any other multilinestring. + The older behavior was an undocumented feature, but people who assumed they had their data stored as LINESTRING + may experience these returning NULL in 2.0 now. @@ -2030,6 +2035,11 @@ POINT(3 2) &sqlmm_compliant; SQL-MM 3: 7.1.3 &Z_support; + Changed: 2.0.0 no longer works with single geometry multilinestrings. In older + versions of PostGIS -- a single line multilinestring would work happily with this + function and return the start point. In 2.0.0 it just returns NULL like any other multilinestring. + The older behavior was an undocumented feature, but people who assumed they had their data stored as LINESTRING + may experience these returning NULL in 2.0 now. -- 2.50.1