Make AsGML execution order predictable (see #3513 again)

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

diff --git a/topology/test/regress/gml.sql b/topology/test/regress/gml.sql
index a0bb3daedf7d0509f4b15992711e859638da6675..4410600f9f6544bf1591d99a1f2e79ff9986b9a5 100644 (file)
--- a/topology/test/regress/gml.sql
+++ b/topology/test/regress/gml.sql
@@ -168,9 +168,12 @@ SELECT feature_name||'-visited', topology.AsGML(feature,
 --           E22-> N8,(N15)
 --           E12-> (N8),(N9)
 SELECT feature_name||'-visited', topology.AsGML(feature,
-       '', 15, 2, 'visited'::regclass) FROM features.land_parcels
-       WHERE feature_name IN ('P1', 'P2')
-       ORDER BY feature_name DESC;
+       '', 15, 2, 'visited'::regclass) FROM
+       (
+        SELECT * FROM features.land_parcels
+        WHERE feature_name IN ('P1', 'P2')
+        ORDER BY feature_name ASC
+       ) foo ORDER BY feature_name DESC;
 
 -- F3F4 visits (F3),(F4)
 SELECT feature_name||'-visited', topology.AsGML(feature,