[postgis-devel] [PostGIS] #1185: Need DropTopoGeometryTable function

PostGIS trac at osgeo.org
Tue Oct 11 00:27:19 PDT 2011


#1185: Need DropTopoGeometryTable function
-------------------------+--------------------------------------------------
 Reporter:  robe         |       Owner:  strk         
     Type:  enhancement  |      Status:  new          
 Priority:  medium       |   Milestone:  PostGIS 2.0.0
Component:  topology     |     Version:  trunk        
 Keywords:               |  
-------------------------+--------------------------------------------------

Comment(by strk):

 Technically, a TopoGeometry is independent from the table it's attached
 to.
 You may have literal TopoGeometry values, or have them used in multiple
 places.

 Substancially a TopoGeometry is fully defined by the relation table AND
 the layer record (which specifies how to interpret the definition).
 Dropping the layer record makes indeed the TopoGeometry definition
 useless.

 I agree on implementing DropTopoGeometryTable, but I feel the need to
 somehow validate TopoGeometry object references (the topology.TopoGeometry
 object type) to catch malformations like the ones introduced by, for
 instance, saving a TopoGeometry object in a private/backup table and then
 dropping the referee using this function thus making the copied
 TopoGeometry a dangling reference.

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


More information about the postgis-devel mailing list