Hello.
You may execute SET FOREIGN_KEY_CHECKS=0; in mysql and then use
source sql.file;. Run mysql with -B command line option.
Terence [EMAIL PROTECTED] wrote:
Hi,
After reading the docs I realise that in order to use mysqldump with
innodb tables i need to include
SET
Terence,
- Original Message -
From: Terence [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Wednesday, December 22, 2004 5:58 AM
Subject: mysqldump and innodb - set foreign_key_checks=0
Hi,
After reading the docs I realise that in order to use mysqldump with
innodb tables i
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 22, 2004 8:15 PM
To: mysql@lists.mysql.com
Subject: Re: mysqldump and innodb - set foreign_key_checks=0
Terence,
- Original Message -
From: Terence [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Wednesday, December 22, 2004 5
Hi,
After reading the docs I realise that in order to use mysqldump with
innodb tables i need to include
SET FOREIGN_KEY_CHECKS=0;
at the top of my dump file. Is there anyway to do this when my slave
starts up or some other way. The dump file is huge and it takes ages to
open and put the line
Daniel Kasak wrote:
Paul DuBois wrote:
If you have problems reloading the table due to the order
in which the InnoDB tables appear in the dump files, add
SET FOREIGN_KEY_CHECKS = 0;
to the beginning of the file before reloading it.
Our backups are quick large - over 500 MB. Opening the file
Paul DuBois wrote:
If you have problems reloading the table due to the order
in which the InnoDB tables appear in the dump files, add
SET FOREIGN_KEY_CHECKS = 0;
to the beginning of the file before reloading it.
Our backups are quick large - over 500 MB. Opening the file and adding
the above
At 10:33 AM +1000 9/18/03, Daniel Kasak wrote:
Paul DuBois wrote:
If you have problems reloading the table due to the order
in which the InnoDB tables appear in the dump files, add
SET FOREIGN_KEY_CHECKS = 0;
to the beginning of the file before reloading it.
Our backups are quick large - over
It looks like the dump works... however the way it is made, there is no
way to use it to recreate the database because key constraints fail. The
dump contains table creations in an order which does not respect key
constraints.
Is there any work around to rebuild a database with innodb tables ?
At 7:13 PM -0400 9/16/03, Irwin Boutboul wrote:
It looks like the dump works... however the way it is made, there is no
way to use it to recreate the database because key constraints fail. The
dump contains table creations in an order which does not respect key
constraints.
If you have problems
Respondendo,
quinta-feira, 6 de março de 2003, 19:06:06, Mensagem Original:
RM I have a DB where all of the tables are InnoDB, and there are a few
RM straightforward FOREIGN KEY constraints. I would like to use mysqldump to
RM back up the data or move it to another machine.
RM The problem I'm
On Friday 07 March 2003 00:06, Rick Mann wrote:
I have a DB where all of the tables are InnoDB, and there are a few
straightforward FOREIGN KEY constraints. I would like to use mysqldump to
back up the data or move it to another machine.
The problem I'm running into is that when I try to
I have a DB where all of the tables are InnoDB, and there are a few
straightforward FOREIGN KEY constraints. I would like to use mysqldump to
back up the data or move it to another machine.
The problem I'm running into is that when I try to import the data using
mysql, the data is imported in the
Rick Mann wrote:
I have a DB where all of the tables are InnoDB, and there are a few
straightforward FOREIGN KEY constraints. I would like to use mysqldump to
back up the data or move it to another machine.
The problem I'm running into is that when I try to import the data using
mysql, the data
Thanks Luciano.
It works.
Iago.
-Mensaje original-
De: Luciano Barcaro [mailto:[EMAIL PROTECTED]]
Enviado el: martes 28 de mayo de 2002 19:21
Para: Iago Sineiro
CC: MySql Mail List
Asunto: Re: Error 1114 when import mysqldump in InnoDB table
Hi,
the internal space for innodb is full
Hi all.
I import a mysqldump from MyISAM database in a new innodb database. It gives
me an error saying that the table is full
ERROR 1114 at line 3035: The table 'LALBARANPR' is full
These are the values for the innodb variables in the my.cnf file:
innodb_data_file_path =
Hi,
the internal space for innodb is full...
create new extends (add another ibdata file and restart the mysql)
to see how much space is free, execute the command:
show table status like 'yourtableinnodb'
Iago Sineiro wrote:
Hi all.
I import a mysqldump from MyISAM database in a new innodb
Hi!
Heikki == Heikki Tuuri [EMAIL PROTECTED] writes:
Heikki Sanja,
Heikki maybe adding some debug code to the client or the server would help? After
Heikki all, the symptom is easy to notice: the client claims the connection to the
Heikki server is broken. Why does it claim that?
This could
Hi Monty!
I am combining two messages into one:
Heikki server is broken. Why does it claim that?
This could happen if some client code set the 'thd-killed' flag.
The main problem here is why we should get this in mysqldump, but
not
in 'mysql'.
Ken, did you get any output from mysqldump
Hi!
On Mon, Jan 21, 2002 at 05:06:41PM -0500, Ken Menzel wrote:
Hi Heikki and All,
Yes, it seems to be a cache problem, it happens to both MyISAM
I can't reproduce this bug.
Can you create test-suit to reproduce this bug and download it to
ftp://support.mysql.com/pub/mysql/secret ?
PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Tuesday, January 22, 2002 3:47 AM
Subject: Re: mysql cache err with mysqldump? was: Innodb funny error
Hi!
On Mon, Jan 21, 2002 at 05:06:41PM -0500, Ken Menzel wrote:
Hi Heikki and All,
Yes, it seems to be a cache problem
Byelkin [EMAIL PROTECTED]
Cc: Heikki Tuuri [EMAIL PROTECTED]; [EMAIL PROTECTED]
[EMAIL PROTECTED]; [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Tuesday, January 22, 2002 4:28 PM
Subject: Re: mysql cache err with mysqldump? was: Innodb funny error
Hi Alexander,
I am not sure I can create a test-suite
All,
Tuesday, January 22, 2002, 12:06:41 AM, you wrote:
KMYes, it seems to be a cache problem,
[]
KM Also it only seems to affect mysqldump!
BTW, once it helped me to solve such a very-very similar problem
by only adding -q to the mysqldump commandline. God knows why was all the
19 small
rows!
--opt is your friend :)
Ken
- Original Message -
From: Egor Egorov [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 22, 2002 10:36 AM
Subject: mysql cache err with mysqldump? was: Innodb funny error
All,
Tuesday, January 22, 2002, 12:06:41 AM, you wrote
Hi Heikki and All,
Yes, it seems to be a cache problem, it happens to both MyISAM
and innodb table types but simply updating one row in the table maks
the error go away. The table names also seems to change (supporting
the cache idea) and it seems to be mostly readonly tables. Also it
only
24 matches
Mail list logo
