From: Regina Obe Date: Sat, 23 Apr 2011 08:19:07 +0000 (+0000) Subject: Add faq about how to get back removed legacy functions X-Git-Tag: 2.0.0alpha1~1744 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=49355b4740e0e7edad2be4b8de595216ec6f8020;p=postgis Add faq about how to get back removed legacy functions git-svn-id: http://svn.osgeo.org/postgis/trunk@7059 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/faq.xml b/doc/faq.xml index 2d3b4ceb6..144826b71 100644 --- a/doc/faq.xml +++ b/doc/faq.xml @@ -3,6 +3,22 @@ PostGIS Frequently Asked Questions + + + My applications and desktop tools worked with PostGIS 1.5,but they don't work with PostGIS 2.0. How do I fix this? + + + + A lot of deprecated functions were removed from the PostGIS code base in PostGIS 2.0. This has affected applications in addition to third-party tools such as + Geoserver, MapServer, QuantumGIS, and OpenJump to name a few. There are a couple of ways to resolve this. For the third-party apps, you can try to upgrade to the latest versions + of these which have many of these issues fixed. For your own code, you can change your code to not use the functions removed. Most of these functions are non ST_ aliases of ST_Union, ST_Length etc. + and as a last resort, install the whole of legacy.sql or just the + portions of legacy.sql you need. + + The legacy.sql file is located in the same folder as postgis.sql. You can install this file after you have installed postgis.sql and spatial_ref_sys.sql + to get back all the 200 some-odd old functions we removed. + + I'm running PostgreSQL 9.0 and I can no longer read/view geometries in OpenJump, Safe FME, and some other tools?