Re: Replication and transaction questions
Hi! - Original Message - From: Jeremy Zawodny [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Wednesday, April 03, 2002 9:00 AM Subject: Re: Replication and transaction questions On Tue, Apr 02, 2002 at 11:49:10AM +0200, Nico Sabbi wrote: ... 2) why are creations of tables and databases non transactional when using InnoDB? Because InnoDB is a transactional table type. I think Nicola means why one cannot rollback a CREATE TABLE, for instance. It is a tradition in transactional databases that database schema changes are run in a kind of auto-commit mode. Providing the capability to roll back a CREATE TABLE would require some extra code in the database server. Is there an options to change this behavior? No. Use a non-transactional table type such as MyISAM. Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936 MySQL 3.23.47-max: up 54 days, processed 1,508,679,843 queries (319/sec. avg) Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, row level locking, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Replication and transaction questions
HI, I have two questions: 1) is there a way to tell my mysql master not to log failed executions, such as creation of existing tables, drop of inexistant databases etc? Each of these operations lock the slave, and I believe that it' conceptually wrong logging them, since they never took place on the master. I didn't find any mention of similar options in the manual, except some options to tell the slave to go on in case of errors (that I don't like). 2) why are creations of tables and databases non transactional when using InnoDB? Is there an options to change this behavior? Thanks Nico - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Replication and transaction questions
On Tue, Apr 02, 2002 at 11:49:10AM +0200, Nico Sabbi wrote: HI, I have two questions: 1) is there a way to tell my mysql master not to log failed executions, such as creation of existing tables, drop of inexistant databases etc? It's been a while since I checked, but it either doesn't log it or it does log it along with the error code so that the slave can make sure it fails too. Each of these operations lock the slave That smells like some other problem going on. 2) why are creations of tables and databases non transactional when using InnoDB? Because InnoDB is a transactional table type. Is there an options to change this behavior? No. Use a non-transactional table type such as MyISAM. Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936 MySQL 3.23.47-max: up 54 days, processed 1,508,679,843 queries (319/sec. avg) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
