Commit dab135ca authored by Sebastien Robin's avatar Sebastien Robin

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
parent 634a2284
...@@ -13,7 +13,8 @@ UPDATE ...@@ -13,7 +13,8 @@ UPDATE
message message
SET SET
date = DATE_SUB(date, INTERVAL <dtml-sqlvar delay type="int"> SECOND), 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 WHERE
1 = 1 1 = 1
<dtml-if processing_node> <dtml-if processing_node>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment