<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Snipplr</title>
<link>http://snipplr.com/language/rails/tags/migrations</link>
<description>Recent snippets posted on Snipplr.com</description>
<language>en-us</language>
<pubDate>Wed, 19 Jun 2013 19:44:35 GMT</pubDate>
<item>
<title>(Rails) Monkeypatch for easier to read migrations - sgtrock</title>
<link>http://snipplr.com/view/25399/monkeypatch-for-easier-to-read-migrations/</link>
<description><![CDATA[ <p>I never can remember the exact name of the exception to call in self.down for a migration that cannot be undone. So I decided to come up with something easier to remember. This feels more "ruby-ish" and "rails-ish" to me, and so far it works just fine. It also displays a message that is easier to pick out amongst all the other migration output on the screen so you can see at a glance that it failed.</p> ]]></description>
<pubDate>Thu, 24 Dec 2009 22:37:41 GMT</pubDate>
<guid>http://snipplr.com/view/25399/monkeypatch-for-easier-to-read-migrations/</guid>
</item>
<item>
<title>(Rails) Use Rake to tear down, build and prepare a DB for testing with AutoTest/ZenTest - noah</title>
<link>http://snipplr.com/view/9128/use-rake-to-tear-down-build-and-prepare-a-db-for-testing-with-autotestzentest/</link>
<description><![CDATA[ <p>Run the following commands in the root of your Rails project.</p> ]]></description>
<pubDate>Mon, 20 Oct 2008 12:05:53 GMT</pubDate>
<guid>http://snipplr.com/view/9128/use-rake-to-tear-down-build-and-prepare-a-db-for-testing-with-autotestzentest/</guid>
</item>
</channel>
</rss>