<?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 2.1 broke my mysql foreign keys!</title>
	<atom:link href="http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/</link>
	<description>News and updates from the people at SmartLogic Solutions</description>
	<lastBuildDate>Fri, 12 Mar 2010 02:06:34 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rails Migrations, MySQL, unsigned integers, primary keys, and a lot of fun times &#124; Snow Giraffe Tech</title>
		<link>http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/comment-page-1/#comment-901</link>
		<dc:creator>Rails Migrations, MySQL, unsigned integers, primary keys, and a lot of fun times &#124; Snow Giraffe Tech</dc:creator>
		<pubDate>Wed, 08 Apr 2009 03:34:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/#comment-901</guid>
		<description>[...] :limit determines the numeric type. Rails introduced smart integer columns in 2.1 which more or less translates to the number of bytes needed for storage. Here&#8217;s a little map taken from the adapter code. Do be careful, however, as some versions of Rails (2.1) break foreign keys. [...]</description>
		<content:encoded><![CDATA[<p>[...] :limit determines the numeric type. Rails introduced smart integer columns in 2.1 which more or less translates to the number of bytes needed for storage. Here&#8217;s a little map taken from the adapter code. Do be careful, however, as some versions of Rails (2.1) break foreign keys. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nigel Sharp</title>
		<link>http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/comment-page-1/#comment-397</link>
		<dc:creator>Nigel Sharp</dc:creator>
		<pubDate>Sun, 12 Oct 2008 09:23:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/#comment-397</guid>
		<description>Thanks for your kind help, I will give that a go. I hadn&#039;t realized that the fix could be implemented in my app&#039;s code, rather than rails itself !
Thanks once again,
Nigel</description>
		<content:encoded><![CDATA[<p>Thanks for your kind help, I will give that a go. I hadn&#8217;t realized that the fix could be implemented in my app&#8217;s code, rather than rails itself !<br />
Thanks once again,<br />
Nigel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Trupiano</title>
		<link>http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/comment-page-1/#comment-390</link>
		<dc:creator>John Trupiano</dc:creator>
		<pubDate>Sat, 11 Oct 2008 13:23:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/#comment-390</guid>
		<description>Hey Nigel,

I continue to use the monkey patch I included at the top and drop it into initializers/.  It seems to be the cleanest and most modular.  Furthermore, when the app is upgraded to 2.2, I simply need to remove that file.

The patch directly to the source that I included at the end requires the least amount of code, but it would probably require you to fork that version of rails and maintain it (because you&#039;ll need that version of rails on any box that will be used to develop/test/run in production), which seems like overkill.

-John</description>
		<content:encoded><![CDATA[<p>Hey Nigel,</p>
<p>I continue to use the monkey patch I included at the top and drop it into initializers/.  It seems to be the cleanest and most modular.  Furthermore, when the app is upgraded to 2.2, I simply need to remove that file.</p>
<p>The patch directly to the source that I included at the end requires the least amount of code, but it would probably require you to fork that version of rails and maintain it (because you&#8217;ll need that version of rails on any box that will be used to develop/test/run in production), which seems like overkill.</p>
<p>-John</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nigel Sharp</title>
		<link>http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/comment-page-1/#comment-389</link>
		<dc:creator>Nigel Sharp</dc:creator>
		<pubDate>Sat, 11 Oct 2008 13:10:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.smartlogicsolutions.com/2008/06/24/rails-21-broke-my-mysql-foreign-keys/#comment-389</guid>
		<description>Hi John,
Is there a best practise workaround for this ? Unfortuneately I&#039;m stuck with Rails 2.1. When I specify foreign keys as :integer, they&#039;re ending up as BIGINT(11) in MySQL, resulting in failure to save my models. Thanks for any help you can give !
Cheers,
Nigel</description>
		<content:encoded><![CDATA[<p>Hi John,<br />
Is there a best practise workaround for this ? Unfortuneately I&#8217;m stuck with Rails 2.1. When I specify foreign keys as :integer, they&#8217;re ending up as BIGINT(11) in MySQL, resulting in failure to save my models. Thanks for any help you can give !<br />
Cheers,<br />
Nigel</p>
]]></content:encoded>
	</item>
</channel>
</rss>
