[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):

 Mark et al.  Attached is the script I was thinking of

 I was trying to figure out how to get the postgis_upgrade.pl to generate
 something like this file, but couldn't figure that out.   In theory as I
 said if we use a

 SELECT postgis_create.. command for creating objects that can't be dropped
 then this would make life easier.

 Right now the upgrade scripts generated by the .pl miss creating operators
 and CASTS and always create new types which means you can never really use
 the postgis_upgrade.sql for micro to micro upgrade for PostGIS 1.4.
 Ideally it should only drop an aggregate if the aggregate structure was
 changed since the version that is installed.  All this can be checked in
 my proposed postgis_create function.

 In writing this up I also see we forgot to delete those st_union_old ...
 etc. aggregates, which the postgis_create I have set to just drop if it
 sees its existence.

 Attached is the script. Right now its just the postgis.sql.in.c with the
 non-function create stuff moved to postgis_create calls.

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