[postgis-tickets] r14878 - Make AsGML execution order predictable (see #3513 again)

Sandro Santilli strk at keybit.net
Mon May 2 10:05:52 PDT 2016


Author: strk
Date: 2016-05-02 10:05:52 -0700 (Mon, 02 May 2016)
New Revision: 14878

Modified:
   trunk/topology/test/regress/gml.sql
Log:
Make AsGML execution order predictable (see #3513 again)

Modified: trunk/topology/test/regress/gml.sql
===================================================================
--- trunk/topology/test/regress/gml.sql	2016-05-02 00:39:15 UTC (rev 14877)
+++ trunk/topology/test/regress/gml.sql	2016-05-02 17:05:52 UTC (rev 14878)
@@ -168,9 +168,12 @@
 --           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,



More information about the postgis-tickets mailing list