Sandro Santilli fe9e336ea9 Error handling refinements in topology.ST_AddEdgeNewFaces (#988) ... Check for given edge having two distinct vertices before getting a new edge id from sequence, and before testing it for crossing nodes (or it'd give a confusing error message). Refine error message about no-segment edges to not talk about nodes. [RT-SIGTA] git-svn-id: http://svn.osgeo.org/postgis/trunk@7253 b70326c6-7e19-0410-871a-916f4a2858ee		2011-05-26 07:26:56 +00:00
..
manage	Tag some functions as STABLE or even IMMUTABLE (from volatile) - see bug #955	2011-05-17 14:42:44 +00:00
query	topology.GetRingEdges() implementation and test. This is the first real user of next_left_edge/next_right_edge fields in the edge table. [RT-SIGTA]	2011-05-18 08:58:34 +00:00
topoelement	Tag some functions as STABLE or even IMMUTABLE (from volatile) - see bug #955	2011-05-17 14:42:44 +00:00
gml.sql	Appropriately tag GML functions as STABLE, IMMUTABLE or VOLATILE - see bug #955	2011-05-17 19:35:20 +00:00
polygonize.sql	Add topology.polygonize(<toponame>) function, see ticket #916	2011-04-19 16:58:42 +00:00
populate.sql	topology.AddEdge: make edge linking self-consistent (each added edge will form a proper loop)	2011-05-19 20:36:47 +00:00
sqlmm.sql	Error handling refinements in topology.ST_AddEdgeNewFaces (#988)	2011-05-26 07:26:56 +00:00