<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Error handling for MySQL applications</title>
	<atom:link href="http://openquery.com/blog/error-handling-for-mysql-applications/feed" rel="self" type="application/rss+xml" />
	<link>http://openquery.com/blog/error-handling-for-mysql-applications</link>
	<description>About MySQL, Drizzle, MariaDB and more!</description>
	<lastBuildDate>Thu, 02 Feb 2012 21:40:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Migrating MySQL MyISAM apps to the InnoDB storage engine &#171; Open Query blog</title>
		<link>http://openquery.com/blog/error-handling-for-mysql-applications/comment-page-1#comment-952</link>
		<dc:creator>Migrating MySQL MyISAM apps to the InnoDB storage engine &#171; Open Query blog</dc:creator>
		<pubDate>Thu, 02 Apr 2009 09:00:48 +0000</pubDate>
		<guid isPermaLink="false">http://openquery.com/blogs/error-handling-for-mysql-applications#comment-952</guid>
		<description>[...] encounter additional error situations when using InnoDB, which it must handle. In my previous post (Error handling for MySQL applications) I already indicated that many apps just don&#8217;t handle errors properly at all. Many errors are [...]</description>
		<content:encoded><![CDATA[<p>[...] encounter additional error situations when using InnoDB, which it must handle. In my previous post (Error handling for MySQL applications) I already indicated that many apps just don&#8217;t handle errors properly at all. Many errors are [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pingback_bot</title>
		<link>http://openquery.com/blog/error-handling-for-mysql-applications/comment-page-1#comment-920</link>
		<dc:creator>pingback_bot</dc:creator>
		<pubDate>Thu, 12 Mar 2009 13:00:03 +0000</pubDate>
		<guid isPermaLink="false">http://openquery.com/blogs/error-handling-for-mysql-applications#comment-920</guid>
		<description>User &lt;lj user=&quot;arjen_lentz&quot;&gt; referenced to your post from &lt;a href=&quot;http://arjen-lentz.livejournal.com/150770.html&quot; rel=&quot;nofollow&quot;&gt;Migrating MySQL MyISAM apps to the InnoDB storage engine&lt;/a&gt; saying: [...] encounter additional error situations when using InnoDB, which it must handle. In my previous post (&lt;a href=&quot;http://arjen-lentz.livejournal.com/150464.html&quot; rel=&quot;nofollow&quot;&gt;Error handling for MySQL applications&lt;/a&gt;) I already indicated that many apps just don&#039;t handle errors properly at all. Many errors are not ... [...]</description>
		<content:encoded><![CDATA[<p>User <lj user="arjen_lentz"> referenced to your post from <a href="http://arjen-lentz.livejournal.com/150770.html" rel="nofollow">Migrating MySQL MyISAM apps to the InnoDB storage engine</a> saying: [...] encounter additional error situations when using InnoDB, which it must handle. In my previous post (<a href="http://arjen-lentz.livejournal.com/150464.html" rel="nofollow">Error handling for MySQL applications</a>) I already indicated that many apps just don&#8217;t handle errors properly at all. Many errors are not &#8230; [...]</lj></p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
