Comments on: A Rails 2.1 case study: upgrading the Insoshi social networking platform

By: Michael Hartl

Michael Hartl — Wed, 07 Oct 2009 22:19:47 +0000

Nope, we never did figure it out. After running the one-time fix, there wasn’t any compelling reason to try.

By: Terri I.

Terri I. — Wed, 07 Oct 2009 18:51:38 +0000

Did you ever figure out why your schema_migrations table was not populated automatically? We just had same problem and would like to understand what happened. The schema_migrations table was created but not updated with the values that had been in the schema_info table (this was part of an upgrade from 1.2 to 2.3).

By: Jedford Seculles

Jedford Seculles — Fri, 05 Jun 2009 05:04:44 +0000

we ran into the same prob as you guys did in your production server; that is – the new schema tables didn’t create successfully. We had to do this manually

If you’re on oracle do this (assuming the schema_info version is 200):

declare
v_target integer := 200;
v_cnt integer := 0;
begin
while v_cnt v_cnt := v_cnt + 1;
insert into schema_migrations values (v_cnt);
end loop;
end;

By: Alex Leverington

Alex Leverington — Tue, 24 Feb 2009 21:47:33 +0000

Thanks for your post. Your notes were useful for us when upgrading to Rails 2.2.2! Another note to add is that if you generate fields with form helper tags and you name the field ‘name[field]‘, Rails222 will generate a field with an id of name_field instead (the name is still ‘name[field]‘). This creates a problem if you’ve got manual JS pointing to ‘name[field]‘. The solution is to manually specify the :id field and/or nest the field in a rails generated form and let rails assign the name/id, or, change all the refs to name_field.

By: mhartl

mhartl — Tue, 19 Aug 2008 00:20:10 +0000

@Brian: I don't think so, but maybe try asking at the Google group.

By: Brian

Brian — Tue, 19 Aug 2008 00:18:50 +0000

All my routing tests failing with the following basic message:

NoMethodError in ‘ItemsController route recognition should generate params { :controller => ‘items’, action => ‘index’ } from GET /items’
undefined method `to_plain_segments’ for #

Anyone else see or have this issue?

By: mhartl

mhartl — Tue, 19 Aug 2008 00:16:34 +0000

@Brian: weird; I thought I cut-and-pasted that, but you’re right: the current RubyGems version is 1.2.0. I’ve updated the post accordingly.

By: Brian

Brian — Mon, 18 Aug 2008 23:56:17 +0000

Is rubygems 1.2.1 out? On rubyforge, I only see 1.2.0 – when I did the gem system update, I ended up on that 1.2.0 version.

By: Running Rails tests with autotest (ZenTest) and RSpec « Insoshi Ruby on Rails blog

Mon, 28 Jul 2008 20:14:47 +0000

[...] autotest — mhartl @ 1:12 pm I recently ran into a problem with autotest (ZenTest) after upgrading to Rails 2.1 and RSpec 1.4.1. Solving it was annoying, so I hope I can save others some trouble. Here’s the [...]

By: mhartl

mhartl — Fri, 18 Jul 2008 20:14:20 +0000

@Evan: Thanks. Fixed. (N.B. I'm pretty sure you meant to leave this comment at Searching a Ruby on Rails application with Sphinx and Ultrasphinx. :-)