#1345 write this off as an observed regression difference and document the behavior...

git-svn-id: http://svn.osgeo.org/postgis/trunk@8484 b70326c6-7e19-0410-871a-916f4a2858ee

diff --git a/doc/reference_accessor.xml b/doc/reference_accessor.xml
index 47fb09042508159babfc6e0c1f33966b16b88d9e..bba4c8812718ca66b7d297d3ad3e8255c621ab22 100644 (file)
--- a/doc/reference_accessor.xml
+++ b/doc/reference_accessor.xml
@@ -292,6 +292,11 @@ ST_Dimension
 
                <para>&sqlmm_compliant; SQL-MM 3: 7.1.4</para>
                <para>&Z_support;</para>
+               <note><para>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.</para></note>
 
          </refsection>
 
@@ -2030,6 +2035,11 @@ POINT(3 2)
 
          <para>&sqlmm_compliant; SQL-MM 3: 7.1.3</para>
          <para>&Z_support;</para>
+         <note><para>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.</para></note>
 
        </refsection>