Re: mysqldump and foreign keys

2006-04-27 Thread Frank
Nico Rittner wrote: > Hi Frank > >> what I meant was: are you sure that the tables which are in your database >> are defined correctly, i.e. have the actions? > Yes, if i try to delete or update a record which is referenced by another > i get mysql error #1217 , which should be correct. > >> mig

Re: mysqldump and foreign keys

2006-04-25 Thread Nico Rittner
Hi Frank > what I meant was: are you sure that the tables which are in your database > are defined correctly, i.e. have the actions? Yes, if i try to delete or update a record which is referenced by another i get mysql error #1217 , which should be correct. > might have been "lost" somewhere. Ca

Re: mysqldump and foreign keys

2006-04-25 Thread Frank
Nico Rittner wrote: > Hallo, > >> Sorry to ask this questions, but are you confident that the action >> clauses work properly, i.e. the tables were created correctly? > > In the case of a crash i need to restore the dump including > the on delete/update clauses. > >> What do you see when you ex

Re: mysqldump and foreign keys

2006-04-25 Thread Nico Rittner
Hallo, > Sorry to ask this questions, but are you confident that the action clauses > work properly, i.e. the tables were created correctly? In the case of a crash i need to restore the dump including the on delete/update clauses. > What do you see when you execute "show create table groups"? C

Re: mysqldump and foreign keys

2006-04-25 Thread Frank
Nico Rittner wrote: > hi, > >> are you using the InnoDB storage engine for your tables? > yes, i do. > > example: > > $ mysqldump -d core groups : > > CREATE TABLE `groups` ( > `id` smallint(5) unsigned NOT NULL default '0', > `name` varchar(32) NOT NULL default '', > `parent_id` smallint(5) u

Re: mysqldump and foreign keys

2006-04-24 Thread Nico Rittner
hi, > are you using the InnoDB storage engine for your tables? yes, i do. example: $ mysqldump -d core groups : CREATE TABLE `groups` ( `id` smallint(5) unsigned NOT NULL default '0', `name` varchar(32) NOT NULL default '', `parent_id` smallint(5) unsigned default NULL, `setting_` text NOT NULL

Re: mysqldump and foreign keys

2006-04-24 Thread Frank
Nico Rittner wrote: > hello, > > does anybody now how mysqldump handles the actions > for 'on delete' and 'on update' ? In my Version 4.1.14 > the action clauses are missing. When reimporting the > dump, how does mysql know about the 'action' when altering > the table with forein keys. > > Thank

Re: mysqldump and Foreign Keys

2005-02-03 Thread Gleb Paharenko
Hello. Put SET FOREIGN_KEY_CHECKS=0 at the top of your dump file. In 4.1, mysqldump puts that automatically to the dump file. See comments at: http://dev.mysql.com/doc/mysql/en/mysqldump.html Michael Satterwhite <[EMAIL PROTECTED]> wrote: > mysqldump backs all of the tables up in alpha

Re: mysqldump and Foreign Keys

2005-02-02 Thread Duncan Hill
On Wednesday 02 February 2005 14:11, Michael Satterwhite might have typed: > mysqldump backs all of the tables up in alphabetic order, including the > table create statements. The problem is that if foreign keys exist on > the tables, the reload will not work unless the backup file is hand > edited

RE: mysqldump and foreign keys

2002-03-19 Thread Chetan Lavti
hi, I am also using the Innodb table type for my database. when I am using the mysqldump for dumping the tables it really doesn't shows the foreign key in the table structure. but if after deleting my previous database I again create my database using the same dumped file and executes the mysql