Multiple table engine

--001517475482c601a80483b70a27
Content-Type: text/plain; charset=ISO-8859-1

Hi

Just looking for some confirmation that under a single database - I assume
it is perfectly normal to have both MyISAM and InnoDB engines for different
tables ? Is there anything I need to be aware of ?

Thanks
Neil

--001517475482c601a80483b70a27--

Re: Multiple table engine

Tompkins Neil wrote:
> Just looking for some confirmation that under a single database - I assume
> it is perfectly normal to have both MyISAM and InnoDB engines for different
> tables ? Is 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 use 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: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: Multiple table engine

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-repl ication.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@gmail.com
http://www.ebergen.net

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

Re: Multiple table engine

--000e0cd6ecda02a7db04849253fc
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Apr 18, 2010 at 9:35 PM, Eric Bergen 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:
>


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

--000e0cd6ecda02a7db04849253fc--