#42 stats_hourly

open
nobody
None
5
2003-06-03
2003-01-30
Brian Aker
No

<jamie_> ok... I'll do this and backport stats into
stats_hourly later

Discussion

  • Jamie McCarthy
    Jamie McCarthy
    2003-05-23

    • assigned_to: jamiemccarthy --> pudge
     
  • Jamie McCarthy
    Jamie McCarthy
    2003-05-23

    Logged In: YES
    user_id=3889

    OK, I am thinking

    (1) create a stats_hourly table into which all the stats
    with "_(00..23)_" now go
    or
    (2) add an "hour" column to the "stats_daily" table, rename
    it to "stats" I guess, and the definition of that column is
    ENUM('00', '01', ... '23', 'all') or something

    Either way, createStatDaily(), addStatDaily(), etc., all get
    a new param and get themselves renamed.

    Here's the thing, do we want to do this? And if so, where do
    we draw the line? The "duration_*" named stats have many
    fields jammed into the "name" column, only one of which is
    hour. If we deem "hour" important enough to be a new column
    in the table, why not static/dynamic, or median/mean, or all
    the rest?

     
  • Chris Nandor
    Chris Nandor
    2003-06-02

    • assigned_to: pudge --> nobody
     
  • Chris Nandor
    Chris Nandor
    2003-06-02

    Logged In: YES
    user_id=3660

    I dunno ... it doesn't seem to me like hourly stats are that
    important. Is something in particular prompting this?

     
  • Chris Nandor
    Chris Nandor
    2003-06-02

    • assigned_to: nobody --> pudge
     
  • Jamie McCarthy
    Jamie McCarthy
    2003-06-03

    Logged In: YES
    user_id=3889

    No, just a desire for tidyness. If it seems unimportant,
    kill it, I won't complain.

     
  • Chris Nandor
    Chris Nandor
    2003-06-03

    Logged In: YES
    user_id=3660

    Make low-priority.

     
  • Chris Nandor
    Chris Nandor
    2003-06-03

    • assigned_to: pudge --> nobody