<?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: Rails, ActiveRecord, MySQL, GUIDs and the rename_column bug</title>
	<atom:link href="http://inodes.org/2008/01/11/rails-activerecord-mysql-guids-and-the-rename_column-bug/feed/" rel="self" type="application/rss+xml" />
	<link>http://inodes.org/2008/01/11/rails-activerecord-mysql-guids-and-the-rename_column-bug/</link>
	<description>Moo - Development, Trouble-shooting and Random thoughts...</description>
	<lastBuildDate>Fri, 20 May 2011 17:36:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Chris Hapgood</title>
		<link>http://inodes.org/2008/01/11/rails-activerecord-mysql-guids-and-the-rename_column-bug/comment-page-1/#comment-2480</link>
		<dc:creator>Chris Hapgood</dc:creator>
		<pubDate>Wed, 25 Feb 2009 14:29:39 +0000</pubDate>
		<guid isPermaLink="false">http://inodes.org/blog/2008/01/11/rails-activerecord-mysql-guids-and-the-rename_column-bug/#comment-2480</guid>
		<description>[Better late than never -it took me a while to get this up on a public repo]

You could also try my uuid_primary_key plugin.  Solves these problems by completely removing the auto_increment primary key.  The primary key is renamed to uuid.  Performance problems with your DB can still result if you are oblivious to the impact of a 36-char string versus an integer.  But my experience with moderately-sized data sets is pretty good.

http://github.com/cch1/uuid_primary_key/tree/master</description>
		<content:encoded><![CDATA[<p>[Better late than never -it took me a while to get this up on a public repo]</p>
<p>You could also try my uuid_primary_key plugin.  Solves these problems by completely removing the auto_increment primary key.  The primary key is renamed to uuid.  Performance problems with your DB can still result if you are oblivious to the impact of a 36-char string versus an integer.  But my experience with moderately-sized data sets is pretty good.</p>
<p><a href="http://github.com/cch1/uuid_primary_key/tree/master" rel="nofollow">http://github.com/cch1/uuid_primary_key/tree/master</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

