From: Eric Bergen Date: April 18 2010 7:35pm Subject: Re: Multiple table engine List-Archive: http://lists.mysql.com/mysql/221284 Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 On Thu, Apr 8, 2010 at 4:02 AM, Jigal van Hemert wrote: > Tompkins Neil wrote: >> >> Just looking for some confirmation that under a single database - I assu= me >> it is perfectly normal to have both MyISAM and InnoDB engines for >> different >> tables ? =A0Is there anything I need to be aware of ? > > In most case no problems. MySQL can mix engines without problems. > Every engine uses it's own specific buffers, so if your database becomes = big > and memory becomes an issue (large buffers needed) it might be handy to u= se > only one engine (so you can set the buffers for the other engine(s) to a > very low number). > On a daily basis I use databases with mixed MyISAM and InnoDB tables. > > -- > Jigal van Hemert. > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: =A0 =A0http://lists.mysql.com/mysql?unsub=3Deric.bergen@g= mail.com > > --=20 Eric Bergen eric.bergen@stripped http://www.ebergen.net