Re: Partitioned table using two storage engines?

[Mattias Jonsson]

This is not in the pipe currently, and to my knowledge it is not in the current roadmap either.

The main problem with this is because of the different properties of different engines, and that the partitioning feature is build as a 'proxy' engine, which makes it hard to give the optimizer and other parts of the server good or even correct info on some properties. As an example InnoDB uses clustered primary key index and MyISAM does not, and that property is used for some variants of sorting etc.

So no, it is currently not in the roadmap, but we have this feature in the back of our heads and are discussing it now and then, so sometime in the future, we will see if we could make it happen :)