<?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: MySQL Error Message Nonsenses</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2008/03/16/mysql-error-message-nonsenses/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2008/03/16/mysql-error-message-nonsenses/</link>
	<description>Everything about MySQL Performance</description>
	<lastBuildDate>Sat, 21 Nov 2009 05:23:57 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Confusing MySQL Replication Error Message &#124; MySQL Performance Blog</title>
		<link>http://www.mysqlperformanceblog.com/2008/03/16/mysql-error-message-nonsenses/comment-page-1/#comment-308919</link>
		<dc:creator>Confusing MySQL Replication Error Message &#124; MySQL Performance Blog</dc:creator>
		<pubDate>Thu, 05 Jun 2008 03:00:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2008/03/16/mysql-error-message-nonsenses/#comment-308919</guid>
		<description>[...] already wrote about some MySQL Error Messages which are confusing, here is one more: PLAIN TEXT [...]</description>
		<content:encoded><![CDATA[<p>[...] already wrote about some MySQL Error Messages which are confusing, here is one more: PLAIN TEXT [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Log Buffer #89: a Carnival of the Vanities for DBAs</title>
		<link>http://www.mysqlperformanceblog.com/2008/03/16/mysql-error-message-nonsenses/comment-page-1/#comment-255160</link>
		<dc:creator>Log Buffer #89: a Carnival of the Vanities for DBAs</dc:creator>
		<pubDate>Fri, 21 Mar 2008 16:55:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2008/03/16/mysql-error-message-nonsenses/#comment-255160</guid>
		<description>[...] Zaitsev at the MySQL Performance Blog talks about ridiculous error messages generated by the database. (Oracle is guilty of this too!) He also has a cool post [...]</description>
		<content:encoded><![CDATA[<p>[...] Zaitsev at the MySQL Performance Blog talks about ridiculous error messages generated by the database. (Oracle is guilty of this too!) He also has a cool post [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David C</title>
		<link>http://www.mysqlperformanceblog.com/2008/03/16/mysql-error-message-nonsenses/comment-page-1/#comment-253741</link>
		<dc:creator>David C</dc:creator>
		<pubDate>Mon, 17 Mar 2008 21:42:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2008/03/16/mysql-error-message-nonsenses/#comment-253741</guid>
		<description>Strange about the SUN/MySQL thing. . . I&#039;ve always said the Java compiler is as good as the MySQL SQL error reporting is bad. Sure, &quot;Cannot resolve symbol&quot; may seem cryptic here or there but sure as hell more hepful than Error 1054, or whatever.

I&#039;m not holding out any hope, though.</description>
		<content:encoded><![CDATA[<p>Strange about the SUN/MySQL thing. . . I&#8217;ve always said the Java compiler is as good as the MySQL SQL error reporting is bad. Sure, &#8220;Cannot resolve symbol&#8221; may seem cryptic here or there but sure as hell more hepful than Error 1054, or whatever.</p>
<p>I&#8217;m not holding out any hope, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2008/03/16/mysql-error-message-nonsenses/comment-page-1/#comment-253633</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Mon, 17 Mar 2008 15:38:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2008/03/16/mysql-error-message-nonsenses/#comment-253633</guid>
		<description>Well...  This tool proved helpful for other programs as well which may also just print OS error code without good explanation.  Though perhaps same applies to them - their messages should have been more user friendly.</description>
		<content:encoded><![CDATA[<p>Well&#8230;  This tool proved helpful for other programs as well which may also just print OS error code without good explanation.  Though perhaps same applies to them &#8211; their messages should have been more user friendly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vide</title>
		<link>http://www.mysqlperformanceblog.com/2008/03/16/mysql-error-message-nonsenses/comment-page-1/#comment-253622</link>
		<dc:creator>Vide</dc:creator>
		<pubDate>Mon, 17 Mar 2008 14:49:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2008/03/16/mysql-error-message-nonsenses/#comment-253622</guid>
		<description>100% agree. The perror program is the classic example of tool that should have never been created because... well,&#039; it&#039;s bloody obvious! Why some automatic program should tell me a number that I have to put into another program to know what the error actually means? Simply give me the reason!</description>
		<content:encoded><![CDATA[<p>100% agree. The perror program is the classic example of tool that should have never been created because&#8230; well,&#8217; it&#8217;s bloody obvious! Why some automatic program should tell me a number that I have to put into another program to know what the error actually means? Simply give me the reason!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
