[postgis-devel] [PostGIS] #195: Implement RFC3

PostGIS trac at osgeo.org
Fri Nov 6 02:53:44 PST 2009


#195: Implement RFC3
----------------------+-----------------------------------------------------
  Reporter:  pramsey  |       Owner:  pramsey      
      Type:  task     |      Status:  reopened     
  Priority:  medium   |   Milestone:  postgis 1.5.0
 Component:  postgis  |     Version:  1.4          
Resolution:           |    Keywords:               
----------------------+-----------------------------------------------------
Changes (by robe):

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

Comment:

 Paul -- hmm don't know what to say, except I'm really concerned about
 people upgrading.  This essentially requires a dump reload of the
 database.  I don't consider this done since you have not addressed the
 upgrade process.

 If you remove all those functions, then that means people upgrading from
 say 1.3 to 1.4 (will be binding to their old versions) without them
 knowing it.  This is an unfortunate side affect of our new approach to
 allow ooexistence of functions.

 With that said -- the upgrade has to be able to drop the one not use and
 rename the function in use and then replace.

 So in short -- unless you've given great thought into this (HINT HINT my
 proposed in
 #202 )

 I don't think you can do this in 1.5.  As we have stated minor versions do
 not require a dump reload though major versions can.

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


More information about the postgis-devel mailing list