[postgis-devel] [PostGIS] #253: Gist causes wrong result from ~=

[PostGIS]

#253: Gist causes wrong result from ~=
----------------------+-----------------------------------------------------
  Reporter:  nicklas  |       Owner:  pramsey      
      Type:  defect   |      Status:  new          
  Priority:  medium   |   Milestone:  postgis 1.3.7
 Component:  postgis  |     Version:  1.3.X        
Resolution:           |    Keywords:               
----------------------+-----------------------------------------------------
Changes (by robe):

  * version:  1.4.X => 1.3.X
  * milestone:  postgis 1.5.0 => postgis 1.3.7

Comment:

 I would say so and definitely put it back for 1.3.7SVN before 1.3 people
 are screwed.
 I don't think there is a way to do this without forcing everyone to dump
 reload or reindex.  I experimented with sneaking it in by dropping cascade
 and rebuilding my indexes (but I guess there is some other stuff besides
 index that a drop cascade does since when I tried to build my index, it
 crashed :().

 Anyway people who upgraded there db from 1.3 to 1.4 without a dump restore
 are probably not affected.  Just new installs I suspect.

 Luckily I have a feeling Kevin, that you and I are in a minority of the
 people who use this operator or really know what it does.  So we can patch
 the ST_OrderingEquals so its not affected and that will alleviate further
 damage for those where the drop operator class is not an option.

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