Regress-test ST_ChangeEdgeGeom with 2-vertext target (#1775)

This case was actually fixed by previous commit (ST_SymDifference)

git-svn-id: http://svn.osgeo.org/postgis/trunk@9642 b70326c6-7e19-0410-871a-916f4a2858ee

NEWS

@@ -3,8 +3,9 @@ PostGIS 2.0.1
 
 * Bug Fixes *
 
-  - #1776, fix ST_SymDifference(empty, geom) to return geom
-  - #1708, improve restore of PosgreSQL 9.1 backups 
+  - #1775, ST_ChangeEdgeGeom collision detection with 2-vertex target.
+  - #1776, fix ST_SymDifference(empty, geom) to return geom.
+  - #1708, improve restore of PosgreSQL 9.1 backups.
   - #1766, don't let ST_RemEdge* destroy peripheral TopoGeometry objects.
   - #1714, more robust handling of high topology tolerance.
   - #1759, loading transformed shapefiles in raster enabled db.

topology/test/regress/st_changeedgegeom.sql

@@ -117,6 +117,10 @@ SELECT 'T11F',
   FROM city_data.face f, city_data.edge e
   WHERE e.edge_id = 16 AND f.face_id = e.left_face;
 
+-- See http://trac.osgeo.org/postgis/ticket/1775
+SELECT 'T12.1', ST_AddIsoNode('city_data', 8, 'POINT(49 10)');
+SELECT 'T12', ST_ChangeEdgeGeom('city_data', 16, 'LINESTRING(47 6, 47 14)');
+
 -- TODO: test changing some clockwise closed edges..
 
 SELECT topology.DropTopology('city_data');

topology/test/regress/st_changeedgegeom_expected

@@ -33,4 +33,6 @@ T10|28
 ERROR:  Edge changed disposition around start node 17
 T11|Edge 16 changed
 T11F|t
+T12.1|23
+ERROR:  Edge motion collision at POINT(49 10)
 Topology 'city_data' dropped