…commanual foreign_key_…innodb_change_bufferingblogpercona.commanual innodb_checksumsblogpercona.commanual innodb_commit_concurrencyblogpercona.commanual innodb_concurrency_ticketsblogpercona.commanual innodb_data_file_pathblogpercona.commanual Innodb_data_fsyncsblogpercona.commanual innodb…
Post: Announcing Percona XtraDB Cluster 5.5.29-23.7.1
January 30, 2013 By 8 Comments
… a delete for a table with foreign key constraint. Bug fixed #1078346 (Seppo Jaakola). When variable innodb_support_xa was set to 0, wsrep position wasn’t stored into the InnoDB tablespace. Bug fixed #1084199 (Teemu Ollakka). Using XtraBackup for State… non-uniform foreign key reference could cause a slave crash. Fixed by using primary key of the child table when appending exclusive key for…
Post: Best kept MySQLDump Secret
March 23, 2012 By 13 Comments
… use mysqldump –single-transaction to get consistent backup for their Innodb tables without making database read only. In most cases it… KEYS */; UNLOCK TABLES; /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY…
Comment: Heikki Tuuri to answer your in depth Innodb questions
September 28, 2007 By 51 Comments
In InnoDB, the referenced columns of a unique constraint need not form a primary key or a unique constraint: it is sufficient… a foreign key not reference an entire primary key or unique constraint (something that is mandatory in every other RDBMS that suppors foreign key constraints…
Comment: Unexpected problem with triggers and mysqldump
February 25, 2013 By 8 Comments
… “–compatible=no_table_options” while dumping data. Make sure that InnoDB is the default engine. The catch is that it will… table to InnoDB I guess this will not be an issue unless you are using UTF-8 data or expect foreign keys. MySQL… no way to disable triggers nor any way to disable foreign key checks completely. http://bugs.mysql.com/bug.php?id=62602
Post: Announcing Percona XtraDB Cluster 5.5.29-23.7.2
February 13, 2013 By Leave a Comment
… to append the key for provider library, which could cause a memory leak. Bug fixed for MyISAM temporary tables, InnoDB temporary tables… #1078346 introduced a regression. Foreign key checks were skipped in the parent table, which would cause the foreign key constraint errors. Bug fixed #1117175…
Comment: How to recover a single InnoDB table from a Full Backup
April 11, 2012 By 10 Comments
Hi, consider this comment about foreign key and transportable tablespaces : “To export tables that are in a foreign key relationship you must export and import all the tables together” Source : http://blogs.innodb.com/wp/2012/04/innodb-transportable-tablespaces/
Post: Beware the Innodb Table Monitor
November 29, 2011 By 2 Comments
… this: =========================================== 090420 12:09:32 INNODB TABLE MONITOR OUTPUT =========================================== ————————————– TABLE: name SYS_FOREIGN, id 0 11, columns 7, …, uniq 2, type 0 root page 47, appr.key vals 1, leaf pages 1, size pages 1 …
Comment: COUNT(*) for Innodb Tables
April 3, 2009 By 32 Comments
…`), KEY `physmessage_id_index` (`physmessage_id`), KEY `physmessage_id_is_header_index` (`physmessage_id`,`is_header`), CONSTRAINT `dbmail_messageblks_ibfk_1` FOREIGN KEY (`physmessage_id`) REFERENCES `dbmail_physmessage` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=602519 DEFAULT…
Comment: INSERT ON DUPLICATE KEY UPDATE and REPLACE INTO
January 22, 2007 By 15 Comments
… key, notid int) type=innodb; Query OK, 0 rows affected, 1 warning (0.07 sec) mysql> create table c (id int primary key, fk int , foreign key (fk) references p(id) on delete CASCADE ) type=innodb; Query OK, 0 rows affected…
