Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
statistics.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
17 Feb 2006 at 20:37 UTC
Updated:
2 Jan 2014 at 23:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
magico commentedComment #2
ChrisBryant commented+1 vote for this as well. Additionally, a setting for archiving the data at an interval would be ideal. That way the table size could be kept down but the data would still exist, maybe downloaded as csv.
Chris
PS: I'm not sure if this should be 5.x-dev or 6.x-dev (probably 6.x I assume but it's set for 5.x for now.)
Comment #3
geodaniel commentedSounds like a sensible suggestion. I'd also like to add a few more options of 26 and 52 weeks to extend it a little.
As for archiving, you could always do that directly from your database as and when required...
(moved to 6.x-dev as no new features will make it into 5.x now as far as I'm aware)
Comment #4
geodaniel commentedI've rolled a patch against current HEAD that:
Comment #5
Chris Johnson commented+1 to the idea of allowing never and longer periods of data collection, e.g. Dan's 26 and 52 week periods.
Patch looks good on inspection (I have not tested it).
Comment #6
geodaniel commentedI've also been thinking of other ways to make it more flexible, so people aren't limited to set periods, and could enter their own. I'm not entirely sure I like it, but one way I thought of doing this would be to have two fields: a text field for an integer and a dropdown selection box with 'seconds', 'minutes', 'hours', 'days', 'weeks', 'months' (? not fixed period) or 'years'.
Comment #7
peterx commentedPatch is working on my 5.0 sites and replaces nicely some code I added to 4.6. For those who want complete control over deletion, the deletion could be moved to a function that is called with the date for deletion. External modules could then request the deletion. The deletion could be added to an archive module that copies the log to an archive then requests the deletion. You would need a matching data request function so someone could request:
Comment #8
ChrisBryant commentedSometimes there is also the need to completely reset, so that might be good to add an option for "Reset Logs" as well. I guess it could be done with the date changes that geodaniel suggested but say to delete at the current date/time.
Comment #9
bdragon commentedPatch no longer applies due to the page split.
Comment #10
dave reidMoving up to Drupal 7.
Comment #11
dave reidAdding the novice tag. Anyone want to pick this up?
Comment #12
davyvdb commentedComment #13
davyvdb commentedWhy not do this for dblog too? http://drupal.org/node/560484
Comment #14
mgifford+1
I like the idea of never discarding it. Patch applies cleanly.
Comment #15
janusman commentedWorks.
Comment #16
webchickMakes sense to me. Committed to HEAD!
Comment #18
ahjota commentedWould like to see this in D6 as well. Doesn't seem too hard, but I don't have any experience with the patch system (yet).
Comment #19
dave reidComment #20
bdragon commentedHere's a quick backport.
Comment #21
jzacsh commentedseems to work. option is available. however, i'm not sure how legitimate of a review this is, seeing as I'd have to set my clock forward on my system, to see if the logs ever get discarded, and thus watch the patch in action/time.
works, though, from what I can tell.
Comment #22
gábor hojtsyCommitted, thanks.