Re: UNIX_TIMESTAMP Duplicate key
Posted by:
Rick James
Date: January 13, 2010 09:08PM
Hmmm... Seems like my suggestion would still work. Note that I included a COUNT in the summary table. If hourly summary has count=3, then the reading was taken every 20 minutes; if count=30, then 2 minutes. (Granted, you could be missing some readings, so that could fail. To handle this, you could have another column that says how frequent the reading was taken. Or simply ignore the question -- max, min, average still work regardless of what the count is.)
Subject
Written By
Posted
Re: UNIX_TIMESTAMP Duplicate key
January 13, 2010 09:08PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.