[postgis-devel] [PostGIS] #541: unique constraint on geography not enforced on update

[PostGIS]

#541: unique constraint on geography not enforced on update
---------------------+------------------------------------------------------
 Reporter:  arno     |       Owner:  pramsey       
     Type:  defect   |      Status:  new           
 Priority:  medium   |   Milestone:  PostGIS Future
Component:  postgis  |     Version:  trunk         
 Keywords:           |  
---------------------+------------------------------------------------------
Changes (by robe):

  * milestone:  PostGIS 2.0.0 => PostGIS Future


Comment:

 Paul -- feel free to move this back if you want.  Just want to gt rid of
 the clutter in our PostGIS 2.0.0 milestone so it includes just things we
 really plan to get done in this release.  This sounds like not a simple
 issue to fix and to me I don't see much benefit in putting a unique
 constraint on a geometry.  Why don't you just use exclusion constaints
 which is what they are designed for and which is designed to use GIST
 indexes.

 http://www.depesz.com/index.php/2010/01/03/waiting-for-8-5-exclusion-
 constraints/

 Granted I think we have issues with that too, but I'd rather deal with
 those issues than btree ones.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/541#comment:4>
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.