<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Pythian Blog &#187; data integrity</title>
	<atom:link href="http://www.pythian.com/news/tag/data-integrity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pythian.com/news</link>
	<description>News and views from Pythian DBAs</description>
	<lastBuildDate>Fri, 10 Feb 2012 09:54:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Apparent vs. actual data integrity</title>
		<link>http://www.pythian.com/news/1463/apparent-vs-actual-data-integrity/</link>
		<comments>http://www.pythian.com/news/1463/apparent-vs-actual-data-integrity/#comments</comments>
		<pubDate>Mon, 26 Jan 2009 04:07:48 +0000</pubDate>
		<dc:creator>Sheeri Cabral</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[data integrity]]></category>
		<category><![CDATA[silent truncation]]></category>

		<guid isPermaLink="false">http://www.pythian.com/blogs/1463/apparent-vs-actual-data-integrity</guid>
		<description><![CDATA[I realized tonight exactly why MySQL&#8217;s default behavior of silent truncation bothers me. It reminds me of people who use a ticketing system and close every ticket as soon as they are done working on the issue instead of actually asking the other party if they are satisfied, because closing more tickets make it look [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/1463/apparent-vs-actual-data-integrity/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>MySQL: RENAME TABLE on Transactional Tables Can Jeopardize Slave Data</title>
		<link>http://www.pythian.com/news/1285/mysql-rename-table-on-transactional-tables-can-jeopardize-slave-data/</link>
		<comments>http://www.pythian.com/news/1285/mysql-rename-table-on-transactional-tables-can-jeopardize-slave-data/#comments</comments>
		<pubDate>Thu, 09 Oct 2008 00:09:16 +0000</pubDate>
		<dc:creator>Raj Thukral</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[data integrity]]></category>
		<category><![CDATA[InnoDB]]></category>
		<category><![CDATA[Replication]]></category>
		<category><![CDATA[replication errors]]></category>
		<category><![CDATA[slave]]></category>

		<guid isPermaLink="false">http://www.pythian.com/blogs/1285/mysql-rename-table-on-transactional-tables-can-jeopardize-slave-data</guid>
		<description><![CDATA[Do you have a master-slave MySQL set up?Â  Ever do DDL changes on the master?Â  You may be hit with a serious data integrity bug.Â  Read on. One of our clients does a regular rename tables on the master to keep the current table small and archive off old data.Â  We&#8217;d occasionally be hit by [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/1285/mysql-rename-table-on-transactional-tables-can-jeopardize-slave-data/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

