]> granicus.if.org Git - postgis/commitdiff
Add changed section for 2.1 and mark ST_Segmentize as having a breaking change
authorRegina Obe <lr@pcorp.us>
Fri, 14 Sep 2012 03:10:41 +0000 (03:10 +0000)
committerRegina Obe <lr@pcorp.us>
Fri, 14 Sep 2012 03:10:41 +0000 (03:10 +0000)
git-svn-id: http://svn.osgeo.org/postgis/trunk@10283 b70326c6-7e19-0410-871a-916f4a2858ee

doc/reference_editor.xml
doc/xsl/postgis_aggs_mm.xml.xsl

index 87a179de83745204cff89b91d9e9808c2cdba277..7c7be2882587ecd1d41dee160668450ebb51ead8 100644 (file)
@@ -1246,6 +1246,8 @@ SELECT ST_AsEWKT(ST_Scale(ST_GeomFromEWKT('LINESTRING(1 2 3, 1 1 1)'), 0.5, 0.75
                        only. For geometry, length units are in units of spatial reference.  For geography, units are in meters.</para>
                        <para>Availability: 1.2.2</para>
                        <para>Enhanced: 2.1.0 support for geography was introduced.</para>
+                       <para>Changed: 2.1.0 As a result of the introduction of geography support: The construct <code>SELECT ST_Segmentize('LINESTRING(1 2, 3 4)',0.5);</code> will result in ambiguous function error.  You need to have properly typed object e.g. a geometry/geography column, use ST_GeomFromText, ST_GeogFromText or
+                               <code>SELECT ST_Segmentize('LINESTRING(1 2, 3 4)'::geometry,0.5);</code></para>
                        <note><para>This will only increase segments.  It will not lengthen segments shorter than
                        max length</para></note>
                </refsection>
index 5cc123653d1ee3b562382cf902b61a183f5e3bba..bceccea95905480d7d719dd0a32c9701eb261507 100644 (file)
                                
                        
                        </sect2>
+                       
+                       <sect2 id="NewFunctions_2_1_Changed">
+                              <title>PostGIS Functions changed behavior in 2.1</title>
+                              <para>The functions given below are PostGIS functions that have changed behavior in PostGIS 2.1 and may require application changes.</para>
+                    <note><para>If you are using a function that you don't see documented,
+                        it's probably deprecated, about to be deprecated, or internal and should be avoided.  If you have applications or tools
+                        that rely on deprecated functions, please refer to <link linkend="legacy_faq" /> for more details.</para></note>
+
+                    <itemizedlist>
+                    <!-- Pull out the purpose section for each ref entry   -->
+                        <xsl:for-each select='//refentry'>
+                            <xsl:sort select="@id"/>
+                            <xsl:variable name="refid">
+                                <xsl:value-of select="@id" />
+                            </xsl:variable>
+                            
+                            <xsl:variable name="refname">
+                                <xsl:value-of select="refnamediv/refname" />
+                            </xsl:variable>
+                    <!-- For each section if there is note about enhanced in this version -->
+                                <xsl:for-each select="refsection">
+                                    <xsl:for-each select="para | */para">
+                                        <xsl:choose>
+                                            <xsl:when test="contains(.,'Changed: 2.0')">
+                                                <listitem><simpara><link linkend="{$refid}"><xsl:value-of select="$refname" /></link> - <xsl:value-of select="." /></simpara></listitem>
+                                            </xsl:when>
+                                        </xsl:choose>
+                                    </xsl:for-each>
+                                </xsl:for-each>
+                        </xsl:for-each>
+                    </itemizedlist>
+             </sect2>
                
                        <sect2 id="NewFunctions_2_0">
                                <title>PostGIS Functions new, behavior changed, or enhanced in 2.0</title>