NYCPHP Meetup

[jsiegel1 at optonline.net]

Thanks! I'll check that out to see if it will help in this situation.

----- Original Message -----
From: Brian Pang <bpang at bpang.com>
Date: Friday, April 11, 2003 10:40 am
Subject: Re: [nycphp-talk] MySQL & 2.5 million rows!

> then perhaps a read of the manual is in order...
> 
> I'd start here
> 
> http://www.mysql.com/doc/en/Backup.html
> 
> 
> > phpMyAdmin is GREAT tool. However, this is something that the "end
> user" (i.e., my client) would be doing and I don't want to allow 
> them to
> use phpMyAdmin. 
> > 
> > I had thought of the the Insert into...select statement but, 
> though I
> hadn't tried it...I was bit concerned since the select statement would
> pull 2.5 million rows...unless MySql is smart enough to handle this
> without running out of memory or temp space.
> > 
> > Jeff
> > 
> > ----- Original Message -----
> > From: Brian Pang <bpang at bpang.com>
> > Date: Friday, April 11, 2003 10:29 am
> > Subject: Re: [nycphp-talk] MySQL & 2.5 million rows!
> > 
> > > phpMyAdmin has a nice tool to do it for you.
> > > 
> > > But this is all that it's really doing.
> > > 
> > > INSERT INTO dbTwo.tableName SELECT * FROM dbOne.tableName
> > > 
> > > 
> > > 
> > > > You read the subject line correctly!!! I'm loading 2.5 
> million rows
> > > from an ASCII file into a MySQL database. So...here's a little
> > > background on what I've done and then a question. (Please keep 
> in mind
> > > I'm a Php/MySQL newbie...though I'm learnin' fast!!)
> > > > 
> > > > I created three tables - data_new, data_old, data_live. The 
> > > Ascii file
> > > gets read, line by line, and inserted into data_new. When it's 
> > > completedand there are no glitches (i.e., no problem with the 
> > > Ascii file), I want
> > > to move the data from data_live to data_old and then move the 
> new data
> > > from data_new to data_live. So...the question...is there a 
> fast 
> > > way to
> > > move the data from one MySQL table to another (from data_new to
> > > data_live) other than walking through data_new row by 
> > > row...creating an
> > > Insert statement on the fly...and then inserting the row into 
> > > data_live?> 
> > > > 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.
> > > > 
> > > > Jeff
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> 
> 
> 
> 
> 
> --- Unsubscribe at http://nyphp.org/list/ ---
> 
> 
>