<?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: Capturing Erroneous Queries with MySQL Proxy</title>
	<atom:link href="http://www.chriscalender.com/?feed=rss2&#038;p=66" rel="self" type="application/rss+xml" />
	<link>http://www.chriscalender.com/?p=66</link>
	<description>Tips and Solutions for MySQL, MySQL Proxy, and other MySQL-related Topics</description>
	<pubDate>Wed, 08 Sep 2010 01:48:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: SELECT RAND() &#187; Blog Archive &#187; Upgrading from MySQL 4 &#8211; user stories</title>
		<link>http://www.chriscalender.com/?p=66&cpage=1#comment-259</link>
		<dc:creator>SELECT RAND() &#187; Blog Archive &#187; Upgrading from MySQL 4 &#8211; user stories</dc:creator>
		<pubDate>Thu, 07 Jan 2010 16:27:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.chriscalender.com/?p=66#comment-259</guid>
		<description>[...] You may want to log a sample of queries on your older setup and replay them on your new setup to catch the errors. Peter suggested using mk-upgrade in the maatkit tool which is a very sensible choice, also on my end I decided to catch live errors using mysql-proxy and the capture filter function. [...]</description>
		<content:encoded><![CDATA[<p>[...] You may want to log a sample of queries on your older setup and replay them on your new setup to catch the errors. Peter suggested using mk-upgrade in the maatkit tool which is a very sensible choice, also on my end I decided to catch live errors using mysql-proxy and the capture filter function. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Writing output to a log file using MySQL Proxy &#171; Chris on MySQL</title>
		<link>http://www.chriscalender.com/?p=66&cpage=1#comment-247</link>
		<dc:creator>Writing output to a log file using MySQL Proxy &#171; Chris on MySQL</dc:creator>
		<pubDate>Mon, 30 Nov 2009 20:57:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.chriscalender.com/?p=66#comment-247</guid>
		<description>[...] Chris on MySQL Tips and Solutions for MySQL, MySQL Proxy, and other MySQL-related Topics      &#171; Capturing Erroneous Queries with MySQL Proxy [...]</description>
		<content:encoded><![CDATA[<p>[...] Chris on MySQL Tips and Solutions for MySQL, MySQL Proxy, and other MySQL-related Topics      &laquo; Capturing Erroneous Queries with MySQL Proxy [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Log Buffer #168: a Carnival of the Vanities for DBAs &#124; Pythian Group Blog</title>
		<link>http://www.chriscalender.com/?p=66&cpage=1#comment-242</link>
		<dc:creator>Log Buffer #168: a Carnival of the Vanities for DBAs &#124; Pythian Group Blog</dc:creator>
		<pubDate>Fri, 06 Nov 2009 17:47:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.chriscalender.com/?p=66#comment-242</guid>
		<description>[...] Mark Leith has been catching erroneous queries, without MySQL proxy, having been inspired by Chris Calender&#8217;s post, Capturing Erroneous Queries with MySQL Proxy. [...]</description>
		<content:encoded><![CDATA[<p>[...] Mark Leith has been catching erroneous queries, without MySQL proxy, having been inspired by Chris Calender&#8217;s post, Capturing Erroneous Queries with MySQL Proxy. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Catching erroneous queries, without MySQL proxy at Xaprb</title>
		<link>http://www.chriscalender.com/?p=66&cpage=1#comment-240</link>
		<dc:creator>Catching erroneous queries, without MySQL proxy at Xaprb</dc:creator>
		<pubDate>Sun, 01 Nov 2009 20:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.chriscalender.com/?p=66#comment-240</guid>
		<description>[...] is now, but the concept remains the same: direct your database traffic through a man-in-the-middle. Chris Calender&#8217;s post on capturing erroneous queries with MySQL Proxy shows one use for Proxy. But wait. MySQL Proxy is just inspecting the MySQL protocol. And unless [...]</description>
		<content:encoded><![CDATA[<p>[...] is now, but the concept remains the same: direct your database traffic through a man-in-the-middle. Chris Calender&#8217;s post on capturing erroneous queries with MySQL Proxy shows one use for Proxy. But wait. MySQL Proxy is just inspecting the MySQL protocol. And unless [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
