Running rake db:reset causes problems

[mbrennan]

In Refinery 1.0.3, the rake db:reset and rake db:setup commands use the schema.rb file to quickly setup a database for production or for other reasons instead of using rake db:migrate. If one needs to rebuild their database, they have to issue:

rake db:drop
rake db:create
rails generate refinerycms
rails generate (other refinery engines)
rake db:migrate
rake db:seed

it'd be easier if refinery supported:
rake db:reset
rake db:seed

[parndt]

The generate commands seem unnecessary, why those too?

[parndt]

Seems like rake db:reset is running the seeds because that's where it breaks for me. I can't figure out a way to make it redo itself so that it knows about meta_keywords (which is included by seo_meta and works when migrating)

[scambra]

It doesn't work with ruby 1.8, instance_methods return a array of strings, seo_meta attributes are symbols. It works in 1.9 because instance_methods return symbols