Changeset 18609 for trunk/ippTools/share/stacktool_definebyquery_part2.sql

Timestamp:

Jul 17, 2008, 4:12:41 PM (18 years ago)

Author:

Paul Price

Message:

That ORDER BY which I claimed was so important wasn't really. I think I was in shaky ground so far as standard SQL is concerned (undefined behaviour). By explicitly taking the MAX, I don't need to ORDER BY and then hope that it chooses the right one. Besides, MAX is faster than ORDER BY.

File:

• trunk/ippTools/share/stacktool_definebyquery_part2.sql (modified) (1 diff)

trunk/ippTools/share/stacktool_definebyquery_part2.sql

@@ -20 +20 @@
     GROUP BY
         stack_id
-    -- This ORDER BY is important: it sets the final num_stack that
-    -- comes out of the top-level GROUP BY.  We want it to be the
-    -- biggest number for a skycell/filter combination.
-    ORDER BY
-        num_stack DESC
         ) AS stackSizes
     -- JOINing the warpsToStack and stackSizes tables