ayanova/devdocs/todo.txt

@@ -455,6 +455,22 @@ todo: 1 MAJOR ISSUE FOR US can't use inteval / timespan the way we have
 	timespan stuff like notifications and contracts etc etc because they don't do epochs greater than weeks?
 	Maybe it's just the age query itself that is affected.
 
+Test query from the "offending" view
+	 SELECT aworkorder.id,
+    aworkorder.serial,    
+    aworkorder.createddate,
+    age(timezone('UTC'::text, now())::timestamp with time zone, aworkorder.createddate) AS expwoage
+   FROM aworkorder;
+
+working:
+ SELECT aworkorder.id,
+    aworkorder.serial,    
+    aworkorder.createddate,
+	now() AS NOW_TEST,
+    age(timezone('UTC'::text, now())::timestamp with time zone, aworkorder.createddate) AS expwoage,	
+	now()-aworkorder.createddate AS WORKS
+   FROM aworkorder;
+
 todo: 1 VERY IMPORTANT test on windows where all paths have spaces, i.e. set the server data path to a location with funky folder names with spaces etc
 	confirm everything in raven that writes to disk still works, logging, backup, attachments, temp files served (reports) etc