[postgis-devel] [PostGIS] #202: upgrade issues

[PostGIS]

#202: upgrade issues
----------------------+-----------------------------------------------------
  Reporter:  robe     |       Owner:  robe         
      Type:  defect   |      Status:  assigned     
  Priority:  medium   |   Milestone:  postgis 1.4.1
 Component:  postgis  |     Version:  trunk        
Resolution:           |    Keywords:               
----------------------+-----------------------------------------------------
Comment (by robe):

 Here is a revised patch to trunk postgis.in.sql.c.

 This does both upgrade as well as doing a fresh install.  Unfortunately it
 seems that the way I did it totally confuses the postgis_upgrade.sql
 generator.

 This does what I described above, but I tested it by upgrading a postgis
 1.4 to 1.5 and creating a postgis 1.5 fresh.  Have to find my old 1.3 data
 to test upgrading, but should work since it recreates aggregates, but only
 creates types if they don't already exist.

 I was thinking we can make it smarter by when we decide to rename
 everything check which functions are used in a type and if we don't like
 the name, rename the function to the new name (of course dropping the new
 name).. Haven't attempted that.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/202#comment:22>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS