<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>View on FromDual GmbH</title><link>https://www.fromdual.com/tags/view/</link><description>Recent content in View on FromDual GmbH</description><generator>Hugo</generator><language>en-GB</language><managingEditor>oli.sennhauser@fromdual.com (Oli Sennhauser)</managingEditor><webMaster>oli.sennhauser@fromdual.com (Oli Sennhauser)</webMaster><copyright>© FromDual GmbH</copyright><lastBuildDate>Thu, 19 Jul 2012 10:12:16 +0000</lastBuildDate><atom:link href="https://www.fromdual.com/tags/view/index.xml" rel="self" type="application/rss+xml"/><item><title>How the MySQL Optimizer with MySQL Cluster is cheating you...</title><link>https://www.fromdual.com/blog/how-the-mysql-optimizer-is-cheating-you/</link><pubDate>Mon, 17 May 2010 20:10:23 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/how-the-mysql-optimizer-is-cheating-you/</guid><description>&lt;p&gt;At a customer we had a nice example of how the MySQL Optimizer is cheating when used in combination with the MySQL Cluster. The customer had queries running not too slow in the development environment but when he tried them on the acceptance test environment (with more data) the query was running much too long which was unacceptable because this query can occur many times per second.&lt;/p&gt;</description></item><item><title>Materialized Views (MV) with MySQL</title><link>https://www.fromdual.com/blog/materialized-views-with-mysql/</link><pubDate>Mon, 06 Nov 2006 20:22:00 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/materialized-views-with-mysql/</guid><description>&lt;p&gt;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 &lt;a href="https://www.fromdual.com/mysql-materialized-views"&gt;build Materialised Views&lt;/a&gt; yourself.&lt;/p&gt;</description></item><item><title>Stealthy migrating MySQL tables and MySQL data access interfaces using enlarged updateable VIEW functionality</title><link>https://www.fromdual.com/blog/stealthy-migrating-mysql/</link><pubDate>Tue, 03 Oct 2006 22:18:00 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/stealthy-migrating-mysql/</guid><description>&lt;p&gt;Applications occasionally require redesign. However, redesigning an application cannot be done in one step because the application is distributed or several versions of applications must be supported. MySQL 5.0 provides the necessary means to stealthy migrate your data. In a short overview let&amp;rsquo;s look at what we plan to do: &lt;a href="http://www.fromdual.com/sites/default/files/stealthy_migration.pdf" target="_blank"&gt;Stealthy Migration&lt;/a&gt; (PDF 98.7 kByte).&lt;/p&gt;</description></item></channel></rss>