<?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: The Hobo Migration Generator</title>
	<atom:link href="http://hobocentral.net/blog/2007/07/06/so-long-migrations/feed/" rel="self" type="application/rss+xml" />
	<link>http://hobocentral.net/blog/2007/07/06/so-long-migrations/</link>
	<description>Hobo - the web app builder for Rails</description>
	<lastBuildDate>Wed, 03 Mar 2010 11:41:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: labrat</title>
		<link>http://hobocentral.net/blog/2007/07/06/so-long-migrations/comment-page-1/#comment-10790</link>
		<dc:creator>labrat</dc:creator>
		<pubDate>Tue, 18 Sep 2007 17:23:50 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/07/06/so-long-migrations/#comment-10790</guid>
		<description>&lt;p&gt;This makes so much more sense rather than using the annotate_models plugin.  Plus, the current migrations clash with the ActiveRecord namespace.  The core team really needs to rethink migrations.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This makes so much more sense rather than using the annotate_models plugin.  Plus, the current migrations clash with the ActiveRecord namespace.  The core team really needs to rethink migrations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://hobocentral.net/blog/2007/07/06/so-long-migrations/comment-page-1/#comment-9886</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 31 Aug 2007 08:00:11 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/07/06/so-long-migrations/#comment-9886</guid>
		<description>&lt;p&gt;patrick - looks like MySQL doesn&#039;t support that&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>patrick &#8211; looks like MySQL doesn&#8217;t support that</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: patrick</title>
		<link>http://hobocentral.net/blog/2007/07/06/so-long-migrations/comment-page-1/#comment-9867</link>
		<dc:creator>patrick</dc:creator>
		<pubDate>Thu, 30 Aug 2007 23:40:17 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/07/06/so-long-migrations/#comment-9867</guid>
		<description>&lt;p&gt;I had a default value on a :text and it screamed at me.&lt;/p&gt;

&lt;p&gt;my model:&lt;/p&gt;

&lt;p&gt;fields do
    name :string, :null =&gt; false
    email :string
    about :text, :default =&gt; &quot;No description available&quot;
    timestamps
  end&lt;/p&gt;

&lt;p&gt;the migration step:&lt;/p&gt;

&lt;p&gt;What now: [g]enerate migrations, generate and [m]igrate now or [c]ancel? m
      create  db/migrate
      create  db/migrate/001&lt;em&gt;create&lt;/em&gt;initial&lt;em&gt;tables.rb
(in /Users/home/Development/test)
== 1 CreateInitialTables: migrating ===========================================
-- create&lt;/em&gt;table(:foomodels)
rake aborted!
Mysql::Error: BLOB/TEXT column &#039;about&#039; can&#039;t have a default value: CREATE TABLE foomodels (&lt;code&gt;id&lt;/code&gt; int(11) DEFAULT NULL auto_increment PRIMARY KEY, &lt;code&gt;name&lt;/code&gt; varchar(255) NOT NULL, &lt;code&gt;email&lt;/code&gt; varchar(255) DEFAULT NULL, &lt;code&gt;about&lt;/code&gt; text DEFAULT &#039;No description available&#039;, &lt;code&gt;created_at&lt;/code&gt; datetime DEFAULT NULL, &lt;code&gt;updated_at&lt;/code&gt; datetime DEFAULT NULL) ENGINE=InnoDB&lt;/p&gt;

&lt;p&gt;Taking out the default value (rming the db/migrate/001&lt;em&gt;create&lt;/em&gt;initial_tables.rb file) and retrying made it go through.  Is there a reason why it died with a default value for :text  ?&lt;/p&gt;

&lt;p&gt;Thanks, Hobo rocks.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I had a default value on a :text and it screamed at me.</p>
<p>my model:</p>
<p>fields do<br />
    name :string, :null =&gt; false<br />
    email :string<br />
    about :text, :default =&gt; &#8220;No description available&#8221;<br />
    timestamps<br />
  end</p>
<p>the migration step:</p>
<p>What now: [g]enerate migrations, generate and [m]igrate now or [c]ancel? m<br />
      create  db/migrate<br />
      create  db/migrate/001<em>create</em>initial<em>tables.rb<br />
(in /Users/home/Development/test)<br />
== 1 CreateInitialTables: migrating ===========================================<br />
&#8211; create</em>table(:foomodels)<br />
rake aborted!<br />
Mysql::Error: BLOB/TEXT column &#8216;about&#8217; can&#8217;t have a default value: CREATE TABLE foomodels (<code>id</code> int(11) DEFAULT NULL auto_increment PRIMARY KEY, <code>name</code> varchar(255) NOT NULL, <code>email</code> varchar(255) DEFAULT NULL, <code>about</code> text DEFAULT &#8216;No description available&#8217;, <code>created_at</code> datetime DEFAULT NULL, <code>updated_at</code> datetime DEFAULT NULL) ENGINE=InnoDB</p>
<p>Taking out the default value (rming the db/migrate/001<em>create</em>initial_tables.rb file) and retrying made it go through.  Is there a reason why it died with a default value for :text  ?</p>
<p>Thanks, Hobo rocks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://hobocentral.net/blog/2007/07/06/so-long-migrations/comment-page-1/#comment-9716</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Mon, 27 Aug 2007 08:14:52 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/07/06/so-long-migrations/#comment-9716</guid>
		<description>&lt;p&gt;Steven - We&#039;ve also had that request from who wants to hook up the migration to a button in an IDE. The problem is that the generator is interactive. If it sees a field named &quot;a&quot; that is not in the database, and a DB column named &quot;b&quot; that is not in the model, it asks you if you are renaming &quot;b&quot; to &quot;a&#039;, or removing &quot;b&quot; and creating &quot;a&quot;.&lt;/p&gt;

&lt;p&gt;The other issue is that I think it&#039;s really important to &lt;em&gt;show&lt;/em&gt; the migration code before generating the files, so folk get a chance to check it&#039;s what they intended.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Steven &#8211; We&#8217;ve also had that request from who wants to hook up the migration to a button in an IDE. The problem is that the generator is interactive. If it sees a field named &#8220;a&#8221; that is not in the database, and a DB column named &#8220;b&#8221; that is not in the model, it asks you if you are renaming &#8220;b&#8221; to &#8220;a&#8217;, or removing &#8220;b&#8221; and creating &#8220;a&#8221;.</p>
<p>The other issue is that I think it&#8217;s really important to <em>show</em> the migration code before generating the files, so folk get a chance to check it&#8217;s what they intended.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Borg</title>
		<link>http://hobocentral.net/blog/2007/07/06/so-long-migrations/comment-page-1/#comment-9707</link>
		<dc:creator>Steven Borg</dc:creator>
		<pubDate>Mon, 27 Aug 2007 01:46:16 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/07/06/so-long-migrations/#comment-9707</guid>
		<description>&lt;p&gt;I&#039;d love to see a switch to make the migration silent.  For instance:&lt;/p&gt;

&lt;p&gt;script/generate hobo&lt;em&gt;migrations my&lt;/em&gt;migration -g (or -c, -m)&lt;/p&gt;

&lt;p&gt;It&#039;s an easy add, but I&#039;m not yet feeling comfortable submitting a possible diff...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;d love to see a switch to make the migration silent.  For instance:</p>
<p>script/generate hobo<em>migrations my</em>migration -g (or -c, -m)</p>
<p>It&#8217;s an easy add, but I&#8217;m not yet feeling comfortable submitting a possible diff&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cakebaker &#187; Should the table definition be in the model?</title>
		<link>http://hobocentral.net/blog/2007/07/06/so-long-migrations/comment-page-1/#comment-8578</link>
		<dc:creator>cakebaker &#187; Should the table definition be in the model?</dc:creator>
		<pubDate>Sat, 04 Aug 2007 15:21:18 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/07/06/so-long-migrations/#comment-8578</guid>
		<description>&lt;p&gt;[...] That&#8217;s a question I ask myself after reading an article about an alternative approach to realize migrations in Rails. With that approach, you define the columns of your table in the model and then you generate the migration files from the model. You no longer have to touch any SQL scripts or to write migration files &#8212; if there are changes in the table definition, you make them in the model. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] That&#8217;s a question I ask myself after reading an article about an alternative approach to realize migrations in Rails. With that approach, you define the columns of your table in the model and then you generate the migration files from the model. You no longer have to touch any SQL scripts or to write migration files &#8212; if there are changes in the table definition, you make them in the model. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thyncology &#187; Blog Archive &#187; Nutech, ad nauseum</title>
		<link>http://hobocentral.net/blog/2007/07/06/so-long-migrations/comment-page-1/#comment-8255</link>
		<dc:creator>thyncology &#187; Blog Archive &#187; Nutech, ad nauseum</dc:creator>
		<pubDate>Mon, 30 Jul 2007 19:26:44 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/07/06/so-long-migrations/#comment-8255</guid>
		<description>&lt;p&gt;[...] So when writing migrations gets you down, know that just around the corner is a whole new sexy migration tool from Tom at Hobo Central. Tom is responsible for the current &#8220;sexy migrations&#8221; trend in Rails and has some amazing ideas. The new tool allows you to define all columns and relationships within the models themselves, and based upon the comparison between current models and previous schema, the migration generator migration files to do all the work of both up and down methods! That&#8217;s right, no more typing redundantÂ  code which is just a mirror of the previous method def! I&#8217;d love to see this implemented in core Rails. Let us pray&#8230; [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] So when writing migrations gets you down, know that just around the corner is a whole new sexy migration tool from Tom at Hobo Central. Tom is responsible for the current &#8220;sexy migrations&#8221; trend in Rails and has some amazing ideas. The new tool allows you to define all columns and relationships within the models themselves, and based upon the comparison between current models and previous schema, the migration generator migration files to do all the work of both up and down methods! That&#8217;s right, no more typing redundantÂ  code which is just a mirror of the previous method def! I&#8217;d love to see this implemented in core Rails. Let us pray&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Carter</title>
		<link>http://hobocentral.net/blog/2007/07/06/so-long-migrations/comment-page-1/#comment-8037</link>
		<dc:creator>Nick Carter</dc:creator>
		<pubDate>Fri, 27 Jul 2007 07:37:32 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/07/06/so-long-migrations/#comment-8037</guid>
		<description>&lt;p&gt;That. Is. Sweet. And I&#039;m almost ready to seriously start playing with Hobo!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>That. Is. Sweet. And I&#8217;m almost ready to seriously start playing with Hobo!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: s.m. koppelman</title>
		<link>http://hobocentral.net/blog/2007/07/06/so-long-migrations/comment-page-1/#comment-8014</link>
		<dc:creator>s.m. koppelman</dc:creator>
		<pubDate>Thu, 26 Jul 2007 20:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/07/06/so-long-migrations/#comment-8014</guid>
		<description>&lt;p&gt;I mean this is nice and all, but who needs to rummage through old migrations to figure out what columns are in a table? Surely you didn&#039;t do all this just because you never noticed the schema.rb/schema.sql file that gets generated after running a migration? :)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I mean this is nice and all, but who needs to rummage through old migrations to figure out what columns are in a table? Surely you didn&#8217;t do all this just because you never noticed the schema.rb/schema.sql file that gets generated after running a migration? :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jabari Zakiya</title>
		<link>http://hobocentral.net/blog/2007/07/06/so-long-migrations/comment-page-1/#comment-7852</link>
		<dc:creator>Jabari Zakiya</dc:creator>
		<pubDate>Sat, 21 Jul 2007 19:55:03 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/07/06/so-long-migrations/#comment-7852</guid>
		<description>&lt;p&gt;Opps. Its Bryan Evans not Bryan Adams.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Opps. Its Bryan Evans not Bryan Adams.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
