Materialized Views on FromDual GmbH

Change MyISAM tables to InnoDB and handle SELECT COUNT(*) situation

oli.sennhauser@fromdual.com (Oli Sennhauser) — Tue, 12 Jun 2012 20:48:38 +0000

Its a known problem that changing the Storage Engine from MyISAM to InnoDB can cause some problems
[ 1
] if you have queries of this type:

Materialized Views with MySQL

oli.sennhauser@fromdual.com (Oli Sennhauser) — Sat, 13 Mar 2010 13:55:05 +0000

Materialized Views (MV) with MySQL

oli.sennhauser@fromdual.com (Oli Sennhauser) — Mon, 06 Nov 2006 20:22:00 +0000

Materialised View (MV) is the pre-calculated (materialised) result of a query. Unlike a simple VIEW the result of a Materialised View is stored somewhere, generally in a table. Materialised Views are used when immediate response is needed and the query where the Materialised View bases on would take to long to produce a result. Materialised Views have to be refreshed once in a while. It depends on the requirements how often a Materialised View is refreshed and how actual its content is. Basically a Materialised View can be refreshed immediately or deferred, it can be refreshed fully or to a certain point in time. MySQL does not provide Materialised Views by itself. But it is easy to build Materialised Views yourself.

Materialized Views on FromDual GmbH

Change MyISAM tables to InnoDB and handle SELECT COUNT(*) situation

Materialized Views with MySQL

Table of Contents

Materialized Views (MV) with MySQL