#5163 rake db:seed should check if the database have pending migrations - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#5163 ✓resolved

rake db:seed should check if the database have pending migrations

Reported by Thiago Pradi | July 20th, 2010 @ 07:04 PM

Hi guys,

I'm using rake db:seed to populate my database, but I found a weird behavior.

The scenario:

tchandy ~ $ rails new sample_application
      create  
      create  README
....
tchandy ~ $ cd sample_application/
tchandy ~/sample_application $ rails g model User name:string
      invoke  active_record
      create    db/migrate/20100720174836_create_users.rb
      create    app/models/user.rb
      invoke    test_unit
      create      test/unit/user_test.rb
      create      test/fixtures/users.yml

This is my seeds.rb:

  User.create!(:name => "Thiago")

When I run:

tchandy ~/sample_application $ rake db:seed   
(in /Users/tchandy/sample_application)
rake aborted!
Could not find table 'users'

(See full trace by running task with --trace)

Is this behaviour normal? My opinion is that rake db:seed should check if the database have pending migrations.

The attached patch checks if the database have pending migrations, and after this, runs the db:seed.