From: Jim McAtee (jmcateemediaodyssey.com)
Date: Sat Jul 02 2005 - 11:30:15 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

No, you don't want a table for each monitor. One table for the data will
be _much_ easier to work with. If you want a history then you need to
insert a new record for each datapoint that you get, with, as Frank
suggested, a date/time column. How large your table will get will depend
on the number of monitors and how often you retrieve data. Depending on
how much history you need to keep, you can periodically trim the table by
deleting all data older than N days (or hours, months, years).

----- Original Message -----
From: "nephish" <nephishxit.net>
To: "mysql" <mysqllists.mysql.com>
Sent: Saturday, July 02, 2005 11:49 AM
Subject: offer a solution ?

> Hey there,
> i have been messing around with MySQL for a little bit now. I have a
> question about how i might could do something.
>
> i am writing a database to track what a bunch of electric monitors are
> doing.
> the status of the monitor changes almost daily. i need access to each
> monitor, when it changed, and i also need to track its history. Easy
> enough. but if i update a row in a table, i loose the old info. So i
> kinda cannot create a table referenced by a key of monitor number... i
> think that the easiest way, would be to create a seperate table for each
> monitor... but there are almost a thousand monitors... will that become
> a nightmare ? can MySQL handle that kind of thing? a thousand tables in
> one database ? i have to be able to access each change in its history.
>
> how should i set this up?
>
> thanks for any suggestions.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]