(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?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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?
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?
Logged In: YES
user_id=3889
No, just a desire for tidyness. If it seems unimportant,
kill it, I won't complain.
Logged In: YES
user_id=3660
Make low-priority.