Re: Multiple table engine

[Johan De Meersman]

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

Re: Multiple table engine

[Eric Bergen]

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 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=eric.ber...@gmail.com
>
>



-- 
Eric Bergen
eric.ber...@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=arch...@jab.org

Re: Multiple table engine

[Jigal van Hemert]

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=arch...@jab.org

回复: Multiple table engine

[Timo]

Different engines' tables have no connect each other.



2010-04-08



Best regards
Timo Seven
blog: http://zauc.wordpress.com
#请翻墙浏览，或者指定hosts到74.200.243.252###
UNIX System Admin & MySQL DBA



发件人: Tompkins Neil 
发送时间: 2010-04-08 18:22
主 题: Multiple table engine
收件人: "[MySQL]" 



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 

Multiple table engine

[Tompkins Neil]

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