Re: Stupid backup/restore question

2002-07-01 Thread Jesse Sheidlower
On Mon, Jul 01, 2002 at 01:23:38PM -0400, Keith C. Ivey wrote: > On 1 Jul 2002, at 12:30, Jesse Sheidlower wrote: > > > What should I be doing instead? The docs don't seem to specify this, > > and there doesn't seem to be an "ignore" or "replace" option for the > > mysql command. Do I actually ha

Re: Stupid backup/restore question

2002-07-01 Thread Thomas Spahni
On Mon, 1 Jul 2002, Jesse Sheidlower wrote: > I have a working server and a development server. From time to time > I'd like to "refresh" the content of my development server with what's > on my working server. So I take one of my regular backups, that I get > by doing "mysqldump database > dbbac

Re: Stupid backup/restore question

2002-07-01 Thread Keith C. Ivey
On 1 Jul 2002, at 12:30, Jesse Sheidlower wrote: > What should I be doing instead? The docs don't seem to specify this, > and there doesn't seem to be an "ignore" or "replace" option for the > mysql command. Do I actually have to drop all the tables on my > development box before loading in from

RE: Stupid backup/restore question

2002-07-01 Thread Cal Evans
use the --opt option for mysqldump. --opt Same as --add-drop-table --add-locks --all --extended-insert --quick --lock-tables Other than that, it's the method I use. =C= * * Cal Evans * Journeyman Programmer * Techno-Mage * http://www.calevans.com *

Re: Stupid backup/restore question

2002-07-01 Thread Mikhail Entaltsev
Jesse, try to make dump (mysqldump) with option "--add-drop-table" or "--opt" (it will be faster). Description of this options see here http://www.mysql.com/doc/m/y/mysqldump.html Best regards, Mikhail. - Original Message - From: "Jesse Sheidlower" <[EMAIL PROTECTED]> To: <[EMAIL PROTEC