Very nice solution. But I just think here, we would have 24 hours accuracy loss?
Say cron ran on "15 March 2012 00:00", now it will next run on "16 March 2012 00:00".
So say some one views any node on "15 March 2012 11:00", the node views between "15 March 2012 00:00" and "15 March 2012 11:00" won't get count, fine?? Since our custom table would get updated on 16 march 00:00, we won't be able to accurately measure the counts for that whole day between cron runs.
Hello Jochen,
Very nice solution. But I just think here, we would have 24 hours accuracy loss?
Say cron ran on "15 March 2012 00:00", now it will next run on "16 March 2012 00:00".
So say some one views any node on "15 March 2012 11:00", the node views between "15 March 2012 00:00" and "15 March 2012 11:00" won't get count, fine?? Since our custom table would get updated on 16 march 00:00, we won't be able to accurately measure the counts for that whole day between cron runs.
Please correct me if I am wrong.
Thanks,
Sajal