From: Stephen Cook (sclistsgmail.com)
Date: Sat Jul 02 2005 - 20:38:26 CDT

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

depending on what you use this information for, you might want to keep
two tables, one with the current information, and one of the history. it
would keep the "current" one relatively small, but allow for looking up
historical data if necessary.

nephish wrote:
> 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.
>
> shawn
>

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

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