Re: Time series database design
Alas there is no standard way to deal with time series in SQL, period. MySQL has no special facilities to handle time. SQL Server 2008 & Oracle do.
A chapter of our book (link below) deals with time & MySQL but not time series.
I've not nearly enough info about your requirement to answer your original question, except to say that repeating observation times needn't violate 2NF, but analysis might be difficult if you store times that way---eg how will you query times for which there is no data? So I would have thought that you begin with tables of all possible dates & times for which there can be data---they're easy to create from as tiny a starting point as a table of no more than ten ints; see "Make a calendar table" at
http://www.artfulsoftware.com/infotree/queries.php?&bw=1276---and join from those tables to your data.
PB
http://www.artfulsoftware.com
Subject
Written By
Posted
Re: Time series database design
August 03, 2008 10:47PM
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.