<?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>tom does things &#187; mysql</title>
	<atom:link href="http://tech.tomgoren.com/archives/tag/mysql/feed" rel="self" type="application/rss+xml" />
	<link>http://tech.tomgoren.com</link>
	<description>useful (?) scripts</description>
	<lastBuildDate>Sat, 01 Oct 2011 18:29:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>MySQL Static Cache Daemon usage example</title>
		<link>http://tech.tomgoren.com/archives/189</link>
		<comments>http://tech.tomgoren.com/archives/189#comments</comments>
		<pubDate>Sat, 09 Jan 2010 16:04:05 +0000</pubDate>
		<dc:creator>tom</dc:creator>
				<category><![CDATA[scripts]]></category>
		<category><![CDATA[daemon]]></category>
		<category><![CDATA[example]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[XML]]></category>

		<guid isPermaLink="false">http://tech.tomgoren.com/?p=189</guid>
		<description><![CDATA[As promised, here is short example of the Daemon in operation. First, in order to generate some data for us to work with, I did the following: This nice page shows us how to get various stock data from Yahoo, who are kind enough to provide an easy-to-access API to their data, and even retrieve [...]]]></description>
		<wfw:commentRss>http://tech.tomgoren.com/archives/189/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MySQL Static Cache Daemon</title>
		<link>http://tech.tomgoren.com/archives/163</link>
		<comments>http://tech.tomgoren.com/archives/163#comments</comments>
		<pubDate>Tue, 05 Jan 2010 09:52:23 +0000</pubDate>
		<dc:creator>tom</dc:creator>
				<category><![CDATA[scripts]]></category>
		<category><![CDATA[/etc/init.d/]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[chkconfig]]></category>
		<category><![CDATA[daemon]]></category>
		<category><![CDATA[init]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[sys-v]]></category>

		<guid isPermaLink="false">http://tech.tomgoren.com/?p=163</guid>
		<description><![CDATA[The problem that this program was designed to solve is a rapidly changing MySQL table in use by a high-traffic website. For instance, stock quotes on the front page of a bank&#8217;s or investments firm&#8217;s site. The data is constantly updated by a service on the backend, and is referred to by some ajax widget [...]]]></description>
		<wfw:commentRss>http://tech.tomgoren.com/archives/163/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MySQL on Windows Batch Backup Script</title>
		<link>http://tech.tomgoren.com/archives/156</link>
		<comments>http://tech.tomgoren.com/archives/156#comments</comments>
		<pubDate>Mon, 30 Nov 2009 19:25:46 +0000</pubDate>
		<dc:creator>tom</dc:creator>
				<category><![CDATA[scripts]]></category>
		<category><![CDATA[batch]]></category>
		<category><![CDATA[mysql]]></category>

		<guid isPermaLink="false">http://tech.tomgoren.com/?p=156</guid>
		<description><![CDATA[Don&#8217;t ask me why scripting in batch is still necessary on the verge of the year 2010, however, what can you do when some clients still use Windows to host their MySQL servers&#8230; REM Simple MySQL backup script per database @echo off REM Set some variables set mysqlcmd=&#34;C:\Program Files\MySQL\MySQL Server 5.0\bin\mysql.exe&#34; set mysqlpwd=amazingsecretsamplepassword set mysqlconnect=%mysqlcmd% [...]]]></description>
		<wfw:commentRss>http://tech.tomgoren.com/archives/156/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>MySQL replication monitoring with Python</title>
		<link>http://tech.tomgoren.com/archives/86</link>
		<comments>http://tech.tomgoren.com/archives/86#comments</comments>
		<pubDate>Mon, 27 Jul 2009 23:21:56 +0000</pubDate>
		<dc:creator>tom</dc:creator>
				<category><![CDATA[scripts]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[replication]]></category>

		<guid isPermaLink="false">http://tech.tomgoren.com/?p=86</guid>
		<description><![CDATA[Setting up a MySQL fail over Master-Master replication system is something one can find many guides for. However, monitoring and recovering from a failure of the system is not as well documented, according to a quick Google search. The top items from that search were: Something called: MYSQL master-master replication monitor shell script that mainly [...]]]></description>
		<wfw:commentRss>http://tech.tomgoren.com/archives/86/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Convert MySQL Tables: MyISAM to InnoDB</title>
		<link>http://tech.tomgoren.com/archives/5</link>
		<comments>http://tech.tomgoren.com/archives/5#comments</comments>
		<pubDate>Mon, 20 Jul 2009 16:47:24 +0000</pubDate>
		<dc:creator>tom</dc:creator>
				<category><![CDATA[scripts]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[innodb]]></category>
		<category><![CDATA[myisam]]></category>
		<category><![CDATA[mysql]]></category>

		<guid isPermaLink="false">http://tech.tomgoren.com/?p=5</guid>
		<description><![CDATA[Not getting into the whole <em>which engine is the best</em> debacle, since obviously, like most important questions in life the answer is: "It depends."

In addition, most of what is written here can be used to convert from <em>any </em>engine to <em>any </em>engine, and thus answering any specific needs your might have.
I needed to convert MyISAM to InnoDB so here it is.

Without further ado...

As far as I know, there are two basic ways to accomplish this:
<ol>
	<li>
<pre lang="SQL"> ALTER TABLE 'tablename' ENGINE = InnoDB</pre>
For each table in the database.</li>
	<li> Dump the table, edit the dump file where it says "CREATE TABLE" and fix to the preferred engine, and then reload the data back into the DB</li>
</ol>
Obviously, these methods are ok when you are dealing with a few tables, however a while ago we had a client with a huge database with over 50 tables, so of course, a script was in place.
]]></description>
		<wfw:commentRss>http://tech.tomgoren.com/archives/5/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

