.. |
addedge.sql
|
topology.AddEdge: correctly handle the case in which a newly added closed edge touches an existing closed edge with an endpoint over a non-endpoint [RT-SIGTA].
|
2011-01-17 08:47:34 +00:00 |
addedge_expected
|
topology.AddEdge: correctly handle the case in which a newly added closed edge touches an existing closed edge with an endpoint over a non-endpoint [RT-SIGTA].
|
2011-01-17 08:47:34 +00:00 |
addface.sql
|
Raise an exception if AddEdge is called on a topology which already defines faces other than the universe face (see #781)
|
2011-01-18 17:19:55 +00:00 |
addface_expected
|
Raise an exception if AddEdge is called on a topology which already defines faces other than the universe face (see #781)
|
2011-01-18 17:19:55 +00:00 |
addnode.sql
|
topology.AddNode: fix detection of edge crossing (#780) [RT-SIGTA]
|
2011-01-17 22:35:50 +00:00 |
addnode_expected
|
topology.AddNode: fix detection of edge crossing (#780) [RT-SIGTA]
|
2011-01-17 22:35:50 +00:00 |
droptopology.sql
|
Fix bug in topology.DropTopology getting confused in presence of multiple topologies [RT-SIGTA]
|
2011-01-07 09:55:00 +00:00 |
droptopology_expected
|
Fix bug in topology.DropTopology getting confused in presence of multiple topologies [RT-SIGTA]
|
2011-01-07 09:55:00 +00:00 |
legacy_invalid.sql
|
Avoid NOTICE messages while running topology tests, make results immune of the number of topologies ever created in the database (helps getting stable results when running the tests manually using run_test directly)
|
2010-12-17 15:17:57 +00:00 |
legacy_invalid_expected
|
ValidateTopology: Put some water on fire by avoiding a full cartesian product scan (#772). It's still too slow, but it is a step forward.
|
2011-01-17 21:03:36 +00:00 |
legacy_predicate.sql
|
Avoid NOTICE messages while running topology tests, make results immune of the number of topologies ever created in the database (helps getting stable results when running the tests manually using run_test directly)
|
2010-12-17 15:17:57 +00:00 |
legacy_predicate_expected
|
Avoid NOTICE messages while running topology tests, make results immune of the number of topologies ever created in the database (helps getting stable results when running the tests manually using run_test directly)
|
2010-12-17 15:17:57 +00:00 |
legacy_query.sql
|
Avoid NOTICE messages while running topology tests, make results immune of the number of topologies ever created in the database (helps getting stable results when running the tests manually using run_test directly)
|
2010-12-17 15:17:57 +00:00 |
legacy_query_expected
|
Avoid NOTICE messages while running topology tests, make results immune of the number of topologies ever created in the database (helps getting stable results when running the tests manually using run_test directly)
|
2010-12-17 15:17:57 +00:00 |
legacy_validate.sql
|
Avoid NOTICE messages while running topology tests, make results immune of the number of topologies ever created in the database (helps getting stable results when running the tests manually using run_test directly)
|
2010-12-17 15:17:57 +00:00 |
legacy_validate_expected
|
Avoid NOTICE messages while running topology tests, make results immune of the number of topologies ever created in the database (helps getting stable results when running the tests manually using run_test directly)
|
2010-12-17 15:17:57 +00:00 |
sqlmm.sql
|
Do not consider DEBUG and NOTICE mesages when running sqlmm regression tests. Should fix #734.
|
2010-12-27 11:05:24 +00:00 |
sqlmm_expected
|
Do not consider DEBUG and NOTICE mesages when running sqlmm regression tests. Should fix #734.
|
2010-12-27 11:05:24 +00:00 |
st_getfacegeometry.sql
|
Make ST_GetFaceGeometry use ST_BuildArea rather than assuming first polygon coming out of Polygonize will be the correct one. Fixes ticket #726. Enables automated testing for it.
|
2010-12-23 12:49:01 +00:00 |
st_getfacegeometry_expected
|
Make ST_GetFaceGeometry use ST_BuildArea rather than assuming first polygon coming out of Polygonize will be the correct one. Fixes ticket #726. Enables automated testing for it.
|
2010-12-23 12:49:01 +00:00 |
topoelement.sql
|
Make the TopoElement domain stricter to forbid arrays with more than 2 elements and also checking the element type being in valid range [RT-SIGTA]
|
2011-01-19 16:46:16 +00:00 |
topoelement_expected
|
Make the TopoElement domain stricter to forbid arrays with more than 2 elements and also checking the element type being in valid range [RT-SIGTA]
|
2011-01-19 16:46:16 +00:00 |
topoelementarray_agg.sql
|
Make the TopoElement domain stricter to forbid arrays with more than 2 elements and also checking the element type being in valid range [RT-SIGTA]
|
2011-01-19 16:46:16 +00:00 |
topoelementarray_agg_expected
|
Make the TopoElement domain stricter to forbid arrays with more than 2 elements and also checking the element type being in valid range [RT-SIGTA]
|
2011-01-19 16:46:16 +00:00 |