Changes between Version 5 and Version 6 of TimeTracking

Timestamp:

Oct 13, 2005, 7:22:44 AM (19 years ago)

Author:

anonymous

Comment:

—

TimeTracking

@@ -122 +122 @@
 
 
+ = Using Postgres with psycho =
+
+Postgres has a few wrinkles and time intervals are not as hard to use.
+{{{
+#!sql
+SELECT DISTINCT 
+   id AS ticket,
+   pl.value::interval  AS planned,
+   s.value::interval AS spent,
+   r.value::interval AS interval,
+  ((s.value::interval + r.value::interval) - pl.value::interval) as accuracy,
+   milestone AS customer,   summary, component, status 
+  FROM enum,ticket t
+  LEFT OUTER JOIN ticket_custom pl ON
+       (t.id=pl.ticket AND pl.name='tt_estimated')
+  LEFT OUTER JOIN ticket_custom s ON
+       (t.id=s.ticket AND s.name='tt_spent')
+  LEFT OUTER JOIN ticket_custom r ON
+       (t.id=r.ticket AND r.name='tt_remaining')
+  ORDER BY milestone;
+
+}}}
+
+
+