Add new comment

Submitted by Sajal (not verified) on Thu, 15/03/2012 - 08:42
 

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

The content of this field is kept private and will not be shown publicly.

Full HTML

  • Lines and paragraphs break automatically.
  • You can caption images (data-caption="Text"), but also videos, blockquotes, and so on.
  • Web page addresses and email addresses turn into links automatically.
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>, <bash>, <cpp>, <css>, <html5>, <java>, <javascript>, <php>, <sql>, <xml>. The supported tag styles are: <foo>, [foo].
CAPTCHA
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.