Context Navigation

Changes between Initial Version and Version 1 of Ticket #5840

Timestamp:: Aug 9, 2007, 8:24:31 AM (17 years ago)
Author:: Noah Kantrowitz
Comment:: It is worth noting that after some standards digging, I found that SELECT ... ORDER BY ... is not actually in any standard, though moving to this CASE based query is closer to the standard at least.

-              initial
+              v1
 The syntax used in ORDER BY in the view ticket queries is not transportable to all DBMSs.
+The syntax used in `ORDER BY` in the view ticket queries is not transportable to all DBMSs.
 I propose to use a CASE WHEN clause instead of ORDER BY (status = 'assigned) -> ORDER BY (CASE WHEN status = 'assigned' THEN 1 ELSE 2 END) DESC
+I propose to use a `CASE WHEN` clause instead of `ORDER BY (status = 'assigned')` -> `ORDER BY (CASE WHEN status = 'assigned' THEN 1 ELSE 2 END) DESC`
 Here's a snippet for the new get_reports:
+{{{
+#!python
 def get_reports(db):
     owner = db.concat('owner', "' *'")
 …
   ORDER BY (CASE WHEN owner = $USER THEN 1 ELSE 2 END), p.value, milestone, t.type, time
 """ % owner))
+}}}