4.0 Migration Issues, FC4, Mysql

Coming from an svn of 2.6, think I was <=1099 …
mysql-4.1.20-1.FC4.1
ruby-libs-1.8.4-3.fc4
ruby-1.8.4-3.fc4

Trying to just upgrade into 4.0 gem caused:

Migrating Typo’s database to newest release
rake aborted!
Multiple migrations have the version number 1

(See full trace by running task with --trace)
/usr/lib/ruby/gems/1.8/gems/typo-4.0.0/./installer/rails-installer.rb:
386:in migrate': Migration failed (RailsInstaller::InstallFailed) from /usr/lib/ruby/gems/1.8/gems/typo-4.0.0/./installer/ rails-installer.rb:520:inin_directory’
from /usr/lib/ruby/gems/1.8/gems/typo-4.0.0/./installer/
rails-installer.rb:384:in migrate' from /usr/lib/ruby/gems/1.8/gems/typo-4.0.0/./installer/ rails-installer.rb:86:ininstall_sequence’
from /usr/lib/ruby/gems/1.8/gems/typo-4.0.0/./installer/
rails-installer.rb:61:in install' from /usr/lib/ruby/gems/1.8/gems/typo-4.0.0/./installer/ rails-installer/commands.rb:54:incommand’
from /usr/lib/ruby/gems/1.8/gems/typo-4.0.0/./installer/
rails-installer.rb:491:in execute_command' from /usr/lib/ruby/gems/1.8/gems/typo-4.0.0/bin/typo:37 from /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/ active_support/dependencies.rb:140:inload’
from /usr/bin/typo:18

If this has no good calls, is there any way to do a import the data
to a fresh install? I dumped my db before all of this.

-a

No insights on this? Any known way of installing a fresh copy and
getting a 2.6 database in there? I’m afraid that in order to install/
upgrade I had to break history and I am caught squarely in limbo
unable to go forward and unable to return to what I had.

-a

You should just be able to download the tar/zip file over the top of
your existing installation and run ‘rake migrate’.

Scott

After getting rake migrate to run I get the following in the
production logs:

ActiveRecord::StatementInvalid (Mysql::Error: Table ‘typo.blogs’
doesn’t exist: SELECT * FROM blogs ORDER BY id LIMIT 1):
.//vendor/rails/activerecord/lib/active_record/
connection_adapters/abstract_adapter.rb:120:in log' .//vendor/rails/activerecord/lib/active_record/ connection_adapters/mysql_adapter.rb:184:inexecute’
.//vendor/rails/activerecord/lib/active_record/
connection_adapters/mysql_adapter.rb:336:in select' .//vendor/rails/activerecord/lib/active_record/ connection_adapters/mysql_adapter.rb:175:inselect_all’
.//vendor/rails/activerecord/lib/active_record/base.rb:390:in
find_by_sql' .//vendor/rails/activerecord/lib/active_record/base.rb:924:infind_every’
.//vendor/rails/activerecord/lib/active_record/base.rb:918:in
find_initial' .//vendor/rails/activerecord/lib/active_record/ base.rb:380:infind’
.//app/models/blog.rb:121:in default' .//app/controllers/application.rb:50:inthis_blog’
.//app/controllers/content_controller.rb:76:in `theme_layout’
[…snip]

Database not get migrated properly?

-a

Ah salvation from friends… Explained my issue to a good rails/ruby
friend and he said Scott has it right, what you need is the migration
to run correctly. You probably have hammed your db up since he
requested that, drop it, add it, remove the old cruft, push in a new
4.0 and show me the migration. I did it, and voila. My site sprang
back to life. I need to change my sidebars call and bring over some
of the custom sidebar work done but BOY-O-BOY I’ve got a grin from
ear to ear.

Thanks Scott (& Jeff!).

-a

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs