Compute boundary date inside priority-computing ZSQLMethods instead of using a separate one.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@19425 20353a03-c40f-0410-a6d1-a30d3c3de9de

product/CMFActivity/Activity/SQLBase.py

@@ -43,8 +43,7 @@ class SQLBase:
     return result[0][0]
 
   def _getPriority(self, activity_tool, method, default):
-    now_date = self.getNow(activity_tool)
-    result = method(to_date=now_date)
+    result = method()
     assert len(result) == 1
     priority = result[0]['priority']
     if priority is None:

product/CMFActivity/skins/activity/SQLDict_getPriority.zsql

@@ -8,11 +8,10 @@ class_name:
 class_file:
 </dtml-comment>
 <params>
-to_date
 </params>
 SELECT MIN(`priority`) AS `priority` FROM
   message
 WHERE
   processing_node = 0
-  AND date <= <dtml-sqlvar to_date type="datetime">
+  AND date <= UTC_TIMESTAMP()
 

product/CMFActivity/skins/activity/SQLQueue_getPriority.zsql

@@ -8,11 +8,10 @@ class_name:
 class_file:
 </dtml-comment>
 <params>
-to_date
 </params>
 SELECT MIN(`priority`) AS `priority` FROM
   message_queue
 WHERE
   processing_node = 0
-  AND date <= <dtml-sqlvar to_date type="datetime">
+  AND date <= UTC_TIMESTAMP()