[drupal-devel] prune tables

Boris Mann borismann at gmail.com
Wed May 11 06:03:04 UTC 2005

On 10-May-05, at 5:47 PM, K B wrote:

>> What I'd rather see is more than one watchdog / accesslog table.
>> There would be a small "current" table. When it has reached maybe 500
>> entries, those get moved to a big backup table and the current  
>> table gets
>> pruned. This could be done by cron. This would require locking, I  
>> think.
>> Which advantages does that have?
>> - We work with a small table on normal page views. Inserts are fast.
>> - We still have all the data we want on admin pages.

Can we/should we dump to disk, like "regular" log files?

The Drupal statistics really aren't very useful right now, other than  
popular files. Either that or I'm too dense to understand the tables  
vs. log file parsers like (e.g.) AWStats.

Boris Mann

More information about the drupal-devel mailing list