if we use timeShift, we should not keep a big number for retry, if we set it...

if we use timeShift, we should not keep a big number for retry, if we set it again to 0, then it should optimize the load of the activity server when there is many messages


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

product/CMFActivity/skins/activity/SQLDict_timeShift.zsql

@@ -13,7 +13,8 @@ UPDATE
   message
 SET
   date = DATE_SUB(date, INTERVAL <dtml-sqlvar delay type="int"> SECOND),
-  processing_date = DATE_SUB(processing_date, INTERVAL <dtml-sqlvar delay type="int"> SECOND)
+  processing_date = DATE_SUB(processing_date, INTERVAL <dtml-sqlvar delay type="int"> SECOND),
+  retry = 0
 WHERE
   1 = 1
 <dtml-if processing_node>