19 messages in com.mysql.lists.mysqlRe: Backing up database
FromSent OnAttachments
toxa...@canada.com06 Jan 2000 22:02 
Uday Kumar Khatua06 Jan 2000 22:23 
manos06 Jan 2000 23:14 
toxa...@canada.com06 Jan 2000 23:46 
toxa...@canada.com06 Jan 2000 23:47 
pe...@torch.blueznet.com07 Jan 2000 00:27 
John Zook07 Jan 2000 02:27 
toxa...@canada.com07 Jan 2000 02:57 
manos07 Jan 2000 03:01 
Uday Kumar Khatua07 Jan 2000 03:13 
Jamie Le Tual07 Jan 2000 04:25 
Paul DuBois07 Jan 2000 08:11 
Stephen Johnson07 Jan 2000 20:44 
toxa...@canada.com07 Jan 2000 20:48 
toxa...@canada.com07 Jan 2000 21:14 
Paul DuBois07 Jan 2000 21:37 
pe...@torch.blueznet.com07 Jan 2000 22:07 
Michael Widenius08 Jan 2000 14:53 
Vivek Khera10 Jan 2000 07:53 
Subject:Re: Backing up database
From:toxa...@canada.com (toxa@canada.com)
Date:01/06/2000 11:47:44 PM
List:com.mysql.lists.mysql

Thank you for all your help. It seems that mysqldump seems to be the answer, but this leads to my next question.

I'm not used to the command line very much and have never done anything with mysql from the command line.

Do I need to connect to the database first?

Or can I just type mysqldump db_name > back_up.sql at the shell prompt. I tried doing the latter and I get

'mysqldump: command not found'

Do I need to do this from the command line?

Does the mysqldump automatically escape all special characters? Or will there be a problem caused by apostrophes etc?

Also, I have used load data infile before to read text files exported from FoxPro to create a database, but how do I create the new database from the list of sql statements the dump creates?

Is that what mysqlimport does? Do I need to do that from the command line?

I guess I should've said questionS. :-)

Thanks

Jennifer