List:General Discussion« Previous MessageNext Message »
From:Johan De Meersman Date:April 19 2010 7:58am
Subject:Re: Multiple table engine
View as plain text  
On Sun, Apr 18, 2010 at 9:35 PM, Eric Bergen <eric.bergen@stripped> wrote:

> This can become a problem when using replication. For example if you do:
>
> begin;
> insert into innodb_table;
> insert into myisam_table;
> insert into innodb_table;
> rollback;
>
> The innodb rows won't be replicated but the myisam row will.  There is
> more info at:
> <http://dev.mysql.com/doc/refman/5.0/en/innodb-and-mysql-replication.html>


That has nothing whatsoever to do with replication, though. The rollback
won't be rolling your MyISAM insert back on the master, either, so the
servers will still be in sync.

This kind of behaviour isn't a mysql issue, it's an operator issue. MyISAM
doesn't magically become transactional because you add InnoDB insert in the
mix.


-- 
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel

Thread
Multiple table engineTompkins Neil8 Apr
  • Re: Multiple table engineJigal van Hemert8 Apr
    • Re: Multiple table engineEric Bergen18 Apr
      • Re: Multiple table engineJohan De Meersman19 Apr