8 Apr
2013
8 Apr
'13
12:32 p.m.
As far as I can tell (when db_mode=3) the timer function calls
synchronize_all_udomains(), which calls get_act_time() and then
db_timer_udomain() in a loop, and db_timer_udomain() just does a
database delete.
Regards,
Peter
On 08/04/13 10:27, Alex Balashov wrote:
On 04/08/2013 04:58 AM, Peter Dunkley wrote:
Hi,
The timer to delete records only runs if the timer_interval modparam is
Peter,
One question that arises with this solution is: what is the full
effect of disabling timer? Is it limited merely to turning off
automatic deletion of expired contacts? Or are there other
'synchronisation' tasks that also don't happen as a result? I have
trouble imagining what those would be in db_mode 3, but still I wonder.
Cheers,
-- Alex
0.
This means you can have multiple active registrars off the same database
table and use some external process to manage deletion of records (for
example, a stored procedure triggered from a cron job).