[postgis-tickets] [PostGIS] #2750: Duplicated DROP AGGREGATE IF EXISTS st_samealignment(raster) in rtpostgis_upgrade_20_21.sql

[PostGIS]

#2750: Duplicated DROP AGGREGATE IF EXISTS st_samealignment(raster) in
rtpostgis_upgrade_20_21.sql
---------------------+------------------------------------------------------
  Reporter:  strk    |       Owner:  dustymugs    
      Type:  defect  |      Status:  reopened     
  Priority:  medium  |   Milestone:  PostGIS 2.1.4
 Component:  raster  |     Version:  2.1.x        
Resolution:          |    Keywords:               
---------------------+------------------------------------------------------
Changes (by strk):

  * status:  closed => reopened
  * resolution:  fixed =>


Comment:

 Actually, reopening as this work would now need to be forward-ported to
 trunk (ouch!).
 Dustymugs, can you help with that, what do you think ?

 The idea is to separate objects that are _required_ to be removed before
 the upgrade from those that can be run after. Any fully obsoleted object
 name can be removed after, while objects having the same name but possibly
 different signature would need to be handled before.

 Handling both before would not hurt (as we have been doing so far) but I
 hope one day to have the "handled-before" ones automated via self-
 contained documentation about which version changed which object signature
 incompatibly...

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2750#comment:11>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.