[postgis-tickets] [PostGIS] #3039: 2.1.2--2.2.0dev: ERROR: operator ~ already exists

[PostGIS]

#3039: 2.1.2--2.2.0dev: ERROR:  operator ~ already exists
-----------------------------------+----------------------------------------
 Reporter:  strk                   |       Owner:  strk 
     Type:  defect                 |      Status:  new  
 Priority:  blocker                |   Milestone:       
Component:  build/upgrade/install  |     Version:  trunk
 Keywords:                         |  
-----------------------------------+----------------------------------------
 Due to my recent commit embedding version information in operators, the
 upgrade from 2.1 to 2.2 broke due to OPERATOR ~(raster,geometry) having a
 "Last Changed: 2.2.0" label on it.

 The problem is that the operator really changed by dropping the COMMUTATOR
 specification (referring to #2532) but such change in an OPERATOR cannot
 currently be correctly injected in a pre-existing database, thus making it
 impossible to correctly upgrade from 2.1 without a dump-reload.

 This ticket is to address the problem in some way.
 We have two options:

  1. Revert the change and postpone it to 3.0
  2. Find a way to provide upgrades for operator definitions

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/3039>
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.