NYCPHP Meetup

[jsiegel1 at optonline.net]

A status table or an additional column that notes whether the data is live/old/new? Keep in mind that the website gets about 1000 inquiries daily that hit this particular table...that's why I thought about 3 separate tables. (Having it all in one table would be about 7.5 million rows).

Jeff

----- Original Message -----
From: nyphp at jimbishop.org
Date: Friday, April 11, 2003 10:30 am
Subject: Re: [nycphp-talk] MySQL & 2.5 million rows!

> > BTW, in case you are wondering why there are three different 
> tables, I
> > felt that this was a better way than my client's present system 
> which> simply wipes out the live data and then reads in the Ascii 
> file. If
> > there is a glitch then they have to empty the table and reload the
> > Ascii. Doing it this way, if they need to go back to the old 
> data, I
> > would move it data from data_old to data_live.
> 
> 
> a better system would be to store all of the data in one table and 
> thenhave a "status" table that kept track of what was live data, 
> old data,
> etc.  then when you want to pull the "live" data, you query the
> "status" table which holds a foreign key to the data table.
> 
> no moving data around.  no duplication of data. 
> 
> 
> 
> 
> 
> 
> 
> --- Unsubscribe at http://nyphp.org/list/ ---
> 
> 
>