From: Regina Obe Date: Fri, 14 Sep 2012 11:29:38 +0000 (+0000) Subject: PostGIS 2.1 changes section was incorrectly listing 2.0 instead of 2.1 changes. ... X-Git-Tag: 2.1.0beta2~647 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b20f89ca3aa071f585d9545c73f35bc69be0edcd;p=postgis PostGIS 2.1 changes section was incorrectly listing 2.0 instead of 2.1 changes. Also just folder 2.1 changes into many What is new in 2.1 section. git-svn-id: http://svn.osgeo.org/postgis/trunk@10286 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/xsl/postgis_aggs_mm.xml.xsl b/doc/xsl/postgis_aggs_mm.xml.xsl index bceccea95..1cead0d9a 100644 --- a/doc/xsl/postgis_aggs_mm.xml.xsl +++ b/doc/xsl/postgis_aggs_mm.xml.xsl @@ -500,42 +500,35 @@ - + + + The functions given below are PostGIS functions that have possibly breaking changes in PostGIS 2.1. If you use any of these, you may need to check your existing code. + + + + + + + + + + + + + + + + + - + + + + + + - - - PostGIS Functions changed behavior in 2.1 - The functions given below are PostGIS functions that have changed behavior in PostGIS 2.1 and may require application changes. - 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 for more details. - - - - - - - - - - - - - - - - - - - - - - - - - - PostGIS Functions new, behavior changed, or enhanced in 2.0