<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Will Maria Live Up To The Hype?</title>
	<link>http://blog.charcoalphile.com/2008/03/21/will-maria-live-up-to-the-hype/</link>
	<description>On Databases, Recovery, Tech</description>
	<pubDate>Thu, 09 Sep 2010 08:30:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Ian Eure</title>
		<link>http://blog.charcoalphile.com/2008/03/21/will-maria-live-up-to-the-hype/#comment-242</link>
		<author>Ian Eure</author>
		<pubDate>Fri, 21 Mar 2008 20:16:01 +0000</pubDate>
		<guid>http://blog.charcoalphile.com/2008/03/21/will-maria-live-up-to-the-hype/#comment-242</guid>
		<description>InnoDB transactions don't work for any operation which changes table structure, so any ALTER/CREATE/DROP TABLE/INDEX statement is non-atomic.

You're right to be skeptical. It seems that every problem MySQL has is solved with yet another storage engine. You end up with a profusion of engines, which are all centered around providing a specific feature, but often lack other features you want.</description>
		<content:encoded><![CDATA[<p>InnoDB transactions don&#8217;t work for any operation which changes table structure, so any ALTER/CREATE/DROP TABLE/INDEX statement is non-atomic.</p>
<p>You&#8217;re right to be skeptical. It seems that every problem MySQL has is solved with yet another storage engine. You end up with a profusion of engines, which are all centered around providing a specific feature, but often lack other features you want.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
