From dab135ca94e6aa480fff453f342f92fdecfc01eb Mon Sep 17 00:00:00 2001 From: Sebastien Robin <seb@nexedi.com> Date: Wed, 22 Feb 2006 10:05:19 +0000 Subject: [PATCH] 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 | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/product/CMFActivity/skins/activity/SQLDict_timeShift.zsql b/product/CMFActivity/skins/activity/SQLDict_timeShift.zsql index 7dc29826b4..fc320591cf 100755 --- a/product/CMFActivity/skins/activity/SQLDict_timeShift.zsql +++ b/product/CMFActivity/skins/activity/SQLDict_timeShift.zsql @@ -13,9 +13,10 @@ 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> AND processing_node = <dtml-sqlvar processing_node type="int"> -</dtml-if> \ No newline at end of file +</dtml-if> -- 2.30.9