From: Paul Ramsey <pramsey@cleverelephant.ca>
Date: Mon, 27 Jun 2011 18:53:49 +0000 (+0000)
Subject: Add migration guide for upgraders
X-Git-Tag: 2.0.0alpha1~1338
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=8a2d7d73d162ed13d80143c0c6253d54975a8a38;p=postgis

Add migration guide for upgraders


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

diff --git a/MIGRATION b/MIGRATION
new file mode 100644
index 000000000..e558c02b7
--- /dev/null
+++ b/MIGRATION
@@ -0,0 +1,35 @@
+PostGIS 2.0 Migration Guide
+===========================
+
+PostGIS 2.0 introduces changes that may affect backward compatibility
+for some applications. This document lists those changes.
+
+
+geometry_columns
+----------------
+
+In PostGIS 2.0, the ``geometry_columns`` metadata has been changed from
+a table to a view. 
+
+  * For applications that manage ``geometry_columns``
+    using the standard AddGeometryColumn() and other methods, there should
+    be no change. 
+
+  * Applications that have inserted directly into ``geometry_columns`` 
+    will need to either move to the standard functions, or change
+    their create table syntax to include type/srid/dimsionality
+    information. 
+
+    For example, to specify a 3D feature in WGS84::
+
+      CREATE TABLE mytable (
+        id SERIAL PRIMARY KEY,
+        g Geometry(PointZ,4326)
+      );
+
+  * Applications reading metadata from ``geometry_columns`` should expect
+    that the geometry type strings will be mixed case and include the
+    dimensionality modifiers. For example: PointZM, MultiLineStringZ.
+
+
+