Michael Stassen wrote:
Before loading the file,
SET FOREIGN_KEY_CHECKS = 0;
after loading the file,
SET FOREIGN_KEY_CHECKS = 1;
That's it! Thanks :)
Even better, upgrade to a newer mysql (4.1.1+), where they are
automatically added to the dump file for you.
Not until the client lib
i think you can use -K on your mysqldump and it'll put the hints in there
for the mysql command to use as well
- Original Message -
From: "Daniel Kasak" <[EMAIL PROTECTED]>
To:
Sent: Thursday, September 29, 2005 7:45 PM
Subject: Backup / Restore database with foreign keys
Greetings
Daniel Kasak wrote:
Greetings.
I've just hit an interesting problem. Luckily I don't actually *need* to
restore from a backup right now - I'm just trying to create a database
dump to submit an unrelated bug report.
Anyway ...
I'm using the command:
mysqldump -K DATABASE_NAME > db.sql -p
H
0;
check the above you will find drop table command in dumpfile.
Thanks
Anil
--
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Monday, January 03, 2005 9:50 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com; [EMAIL PROTECTED]
Subje
line 161: Duplicate entry '77' for key 1
Please advise me, how to suppress the above error messages.
While taking backup used
mysqldump -uMNMSDBA -pMNMSDBA --databases mnms --add-locks
--disable-keys -f --tables ALARM ALARM_CATEGORY ALARM_REPORT
ALARM_REPORT_CATEGORY ALARMINFO >
OTECTED]
Sent: Monday, January 03, 2005 7:03 PM
To: Lakshmi NarasimhaRao (WT01 - TELECOM SOLUTIONS);
[EMAIL PROTECTED]
Cc: mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: RE: backup/restore
Hi,
with which options of mysqldump you have taken backup. if you
use --add-drop-table option then it wi
store
it from backup file.
Thanks
Anil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Monday, January 03, 2005 12:58 PM
To: [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: RE: backup/restore
Hi,
Thank you for your reply. If I
Ligaya Turmelle wrote:
I'm a beginner - but can't you also use mysqlimport?
Not in the case when you have made a backup using mysqldump while using
the default options. mysqlimport is a front end for LOAD DATA INFILE
(http://dev.mysql.com/doc/mysql/en/LOAD_DATA.html)
It is usefule when you hav
[EMAIL PROTECTED] wrote:
Hi,
Thank you for your reply. If I have the create table info in my
dump file, while doing the restore using mysql dbname < dump.dmp, I am
getting errors like
mysql -uMNMSDBA -pMNMSDBA -f mnms <
c:\progra~1\mitel\opsman~1\temp\almhist.dmp
ERROR 1050 at line 11: Tabl
-uMNMSDBA -pMNMSDBA --databases mnms --add-locks
--disable-keys -f --tables ALARM ALARM_CATEGORY ALARM_REPORT
ALARM_REPORT_CATEGORY ALARMINFO >
c:\progra~1\mitel\opsman~1\temp\almhist.dmp
Please help me in this.
Thanks,
Narasimha
-Original Message-
From: Tom Crimmins [mailto:[EMA
I'm a beginner - but can't you also use mysqlimport?
Respectfully,
Ligaya Turmelle
Tom Crimmins wrote:
[snip]
I am doing backup for tables using Mysqldump. But while doing the restore I
am not able to do that using the same Mysqldump. Could you please help me in
that.
[/snip]
mysqldump is not inten
[snip]
I am doing backup for tables using Mysqldump. But while doing the restore I
am not able to do that using the same Mysqldump. Could you please help me in
that.
[/snip]
mysqldump is not intended to be used for the restore.
You need to run the following:
mysql -D dbname < mysqldumpfile
You
I would strongly recommend proving that your solution will work acceptably
by testing it first; don't just assume that all will go well or that we can
anticipate all the problems sight unseen.
Make small test copies of your databases first and then try doing backups
and restores to verify that you
"DANIELE Paolo" <[EMAIL PROTECTED]> wrote:
>
> I have a version of MySQL on my server (mysql Worm 11.18 Distrib
> 3.23.56, for PC-linux (i686)) which I wish to transfer towards a more
> recent server (mysql Ver 11.18 Distrib 3.23.58, for PC-linux (i686)). I
> make a complete backup of the data wi
rently it's in d:\mysql\bin
Pete
Original Message ----
Subject: RE: backup/restore of mysql
Date: Tue, 10 Jul 2001 17:48:31 +0100
From: Simon Green <[EMAIL PROTECTED]>
To: "'Pete Kuczynski'" <[EMAIL PROTECTED]>
Hi Pete
To emable loffing use the --
Greg Cope wrote:
> Pete Kuczynski wrote:
>
>> Hi,
>> I've posted this question before, and some were kind enough to respond
>> with suggestions to my question [replication], but I'm looking for
>> something more difinitave.
>>
>> Background: I'm running a production mysql database/php4/Apache
Pete Kuczynski wrote:
>
> Hi,
> I've posted this question before, and some were kind enough to respond
> with suggestions to my question [replication], but I'm looking for
> something more difinitave.
>
> Background: I'm running a production mysql database/php4/Apache on a NT4
> IBM Netfinity se
y 2001 17:51
> To: Simon Green
> Subject: Re: backup/restore of mysql
>
> Hi,
> do I need to generate these logs using the my.ini file on NT.
>
> Pete
>
> Simon Green wrote:
> >
> > You can use update/bin_update logs.
> > Run these logs from the
You can use update/bin_update logs.
Run these logs from the time of the last backup and it should take you DB up
to date till the time in went down
Simon
PS update logs have all the SQL statements in them so it should be very
simple to recover!
-Original Message-
From: Pete Kuczy
Hi!
At 05:44 PM 6/1/01 +0400, you wrote:
>Hello mysql,
>
> Today I played a little bit with two different ways of backup -
> first one is to use BACKUP TABLE (which works for myisam only) and
> the second one is SAVE DATA/LOAD DATA.
>
> In both cases if I'm not mistaken the file is wrote by m
Peter Zaitsev writes:
> Hello mysql,
>
> Today I played a little bit with two different ways of backup -
> first one is to use BACKUP TABLE (which works for myisam only) and
> the second one is SAVE DATA/LOAD DATA.
>
> In both cases if I'm not mistaken the file is wrote by mysqld server
21 matches
Mail list logo
