<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Ruby on Angus Thinks</title>
		<link>https://www.malcolmhardie.com/weblogs/angus/tags/ruby/</link>
		<description>Recent content in Ruby on Angus Thinks</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
			<copyright>@2026 Angus Hardie</copyright>
		
		
			<lastBuildDate>Fri, 26 Feb 2010 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.malcolmhardie.com/weblogs/angus/tags/ruby/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Rails Migrations and Schemas</title>
				<link>https://www.malcolmhardie.com/weblogs/angus/posts/2010/02/26/rails-migrations-and-schemas/</link>
				<pubDate>Fri, 26 Feb 2010 00:00:00 +0000</pubDate>
				<guid>https://www.malcolmhardie.com/weblogs/angus/posts/2010/02/26/rails-migrations-and-schemas/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;A schema.rb file is typically a ruby script containing a call to the ActiveRecord::Schema.define method.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;A rails migration is a ruby class which inherits from ActiveRecord::Migration and contains a method called up&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The useful fact that I realized only after doing some ultimately unnecessary work today is that because the schema file contains a method call, it&amp;rsquo;s actually easier to extract the information from it than with a migration (which needs SQLEditor to figure out a class name and then call the up method)&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
