<?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: 在Migration中操作新添加的字段</title>
	<atom:link href="http://www.letrails.cn/archives/manipulate-new-added-field-in-migration/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.letrails.cn/archives/manipulate-new-added-field-in-migration/</link>
	<description></description>
	<lastBuildDate>Mon, 02 Jan 2012 01:59:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Yuanyi</title>
		<link>http://www.letrails.cn/archives/manipulate-new-added-field-in-migration/comment-page-1/#comment-296</link>
		<dc:creator>Yuanyi</dc:creator>
		<pubDate>Tue, 27 May 2008 14:09:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.letrails.cn/archives/manipulate-new-added-field-in-migration#comment-296</guid>
		<description>我用2.0.2，不会提示出错，但是first_name得不到保存，然后name就被删了。

reset_column_information比较有用</description>
		<content:encoded><![CDATA[<p>我用2.0.2，不会提示出错，但是first_name得不到保存，然后name就被删了。</p>
<p>reset_column_information比较有用</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sean</title>
		<link>http://www.letrails.cn/archives/manipulate-new-added-field-in-migration/comment-page-1/#comment-295</link>
		<dc:creator>sean</dc:creator>
		<pubDate>Tue, 27 May 2008 09:05:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.letrails.cn/archives/manipulate-new-added-field-in-migration#comment-295</guid>
		<description>数据库中所有用户的名字信息不会丢失吧?在调用&quot;remove_column :profiles, :name&quot;之前，migration 会因为找不到first_name方法退出.

用Profile.reset_column_information也可以的.</description>
		<content:encoded><![CDATA[<p>数据库中所有用户的名字信息不会丢失吧?在调用&#8221;remove_column :profiles, :name&#8221;之前，migration 会因为找不到first_name方法退出.</p>
<p>用Profile.reset_column_information也可以的.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yuanyi</title>
		<link>http://www.letrails.cn/archives/manipulate-new-added-field-in-migration/comment-page-1/#comment-293</link>
		<dc:creator>yuanyi</dc:creator>
		<pubDate>Thu, 22 May 2008 11:06:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.letrails.cn/archives/manipulate-new-added-field-in-migration#comment-293</guid>
		<description>我也认为Migration不应该操作数据，但有些情况下在Migration里直接操作会简单一些，尤其是涉及到部署的时候</description>
		<content:encoded><![CDATA[<p>我也认为Migration不应该操作数据，但有些情况下在Migration里直接操作会简单一些，尤其是涉及到部署的时候</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leondu</title>
		<link>http://www.letrails.cn/archives/manipulate-new-added-field-in-migration/comment-page-1/#comment-292</link>
		<dc:creator>leondu</dc:creator>
		<pubDate>Thu, 22 May 2008 08:52:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.letrails.cn/archives/manipulate-new-added-field-in-migration#comment-292</guid>
		<description>其实我觉得数据操作放在migration里面不合适，migration关注数据结构的操作，而不是数据的操作。

数据操作用rake task来做更加合适。</description>
		<content:encoded><![CDATA[<p>其实我觉得数据操作放在migration里面不合适，migration关注数据结构的操作，而不是数据的操作。</p>
<p>数据操作用rake task来做更加合适。</p>
]]></content:encoded>
	</item>
</channel>
</rss>

