similar to: rake db:redo & rake migrations:reset - or how to cope with the change of db:reset

If I manually drop the database, and run create, then migrate it works fine. But doing a: rake db:reset it fails with: unknown attribute: user_status Does this mean my migrations are not dropping things correctly? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

Would it make sense for rake db:migrate to support creating databases if it is not found, with blessing from user to prevent typos, or as an additional command line switch. Or am I just being too lazy? -- Posted via http://www.ruby-forum.com/.

I''m having a great deal of trouble getting rake to run migrations on our staging server. Everything works fine on my dev box, but trying to run the following on staging results in errors. ----- > rake db:migrate (in /var/www/apps/acadtech2/app) rake aborted! Don''t know how to build task ''db:migrate'' (See full trace by running task with --trace) ---- The

anyone able to explain logic behind "rake spec" startup? i.e. the below steps & why things occur when they do Macintosh-2:myequity greg$ rake spec --trace (in /Users/greg/source/myequity) ** Invoke spec (first_time) ** Invoke db:test:prepare (first_time) ** Invoke db:abort_if_pending_migrations (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute

Hi! Up to now, i had no problems with my migrations and rake (rake db:migrate). Today, i got a project from a svn repository, but i can''t do "rake db:migrate": "rake aborted! No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb) /opt/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1822:in `load_rakefile'' (See full trace by running task

How to empty DB in heroku<http://stackoverflow.com/questions/4820549/how-to-empty-db-in-heroku> I have a Postgres database on Heroku. It is one of the free beta ones. Locally, when testing, I often run rake db:drop && rake db:create && rake db:migrate as a way to reset the database. However, when I try to run this on Heroku, I get the error:\[code\]Couldn''t drop

I recently submitted ticket #9240 (1) adding Oracle support for the rake db:reset task. I don''t consider myself an Oracle expert by any means, and would appreciate if someone familiar with the database can take a look and verify that I''m going in the right direction. Thanks. 1. http://dev.rubyonrails.org/ticket/9240 -- Josh Knowles joshknowles@gmail.com

Hi all, I am facing a problem while using rails "migrate" feature for creating tables in a database. Following are the details. I have 2 applications say "app1" & "app2". I want both of them to use same database say "testdb". For "app1", I create 3 models which in turn create 3 migration files with prefix, 001_, 002_ & 003_. Now I

Hi there - I''m a ruby newbie and am stuck on the Getting Started with Rails app. See output below. Problem arose when I ran the rake db:migrate command. I also tried the ''rake db:migrate RAILS_ENV=development'' command which may be obvious. Any ideas on how to fix this? Many thanks!! $ ruby -v ruby 1.9.3p392 (2013-02-22 revision 39386) [x86_64-darwin10.8.0]

Hi-- I''m trying to do a first migration (2.3.5). I generated a model "Video", but when I try to migrate I get "uninitialized constant Videos". Why is it trying to find a plural class name? Here''s more complete output: trans@logisys:models$ rake db:migrate --trace ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment **

I recently upgraded Cucumber gem from 0.1.16 to 0.3.11. I ran ruby script/generate cucumber. When I ran rake features I received an error telling me I had pending migrations and should run rake db:migrate. I ran rake db:migrate despite fact that my db is up to date. I was confused that the migrations ran from the beginning. However the migrations seem to have no effect on my database.

Hey Folks, RoR noob here with a quick question. I have added a field to a table using: ruby script/generate migration add_price_to_product price:decimal, and did: rake db:migrate afterwards. no change was reflected in the "Views" though. I''m pretty sure i''m missing something here, can anyone give me a pointer? Many Thanks... John -- You received this message

Is there any reason why db:setup and db:reset don''t show any more on "rake -T db"? I guess any rake task that is defined only as a group of other tasks (without any ruby blocks attached) presents this problem. Also let me write this as a remember note to myself for when I have some time: the Rails Guides on Migrations should be updated to include instructions about db:load

Hey all, I''m trying to create a task that prepare the environment to start programming. To do so, I created a task like this *task :setup_env => [''db:reset'', ''db:migrate'', ''db:test:prepare'']* and observed that after execute * rake setup_env*, it never execute db:test:prepare properly. In order to get the schema cloned to test db,

I am beginner for this Rails from the past 2 days I am working hard to fix the following error C:\Murali Rubby\demo\library>rake db:migrate --trace (in C:/Murali Rubby/demo/library) ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:migrate == CreateBooks: migrating ==================================================== --

My migrations were working fine until today. I dropped and re-created the database.But, when I go to apply my migrations, rake migrate aborts with this error. You have a nil object when you didn''t expect it! You might have expected an instance of Array. The error occured while evaluating nil.first Any idea what might be wrong? The migrations look right. It''s talking to the

I ran into the following error: WARNING: ''require ''rake/rdoctask'''' is deprecated. Please use ''require ''rdoc/tas k'' (in RDoc 2.4.2+)'' instead. at /usr/lib/ruby/vendor_ruby/rake/rdoctask.rb rake aborted! uninitialized constant Gem ---- Following that advice (which I also found by searching the web for the error

Hi, I''m new to rspec. I have some fixtures in /spec/fixtures. If they were in /test/fixtures they could be loaded with rake db:fixtures:load. Is there any way other than a symlink to load my rspec fixtures into the database with rake? Or, can I cause rspec to load the fixtures from /test/fixtures? Thanks, Paul

Dumb question, but when you do ''rake migrate'', which database is affected (e.g. test, development, or production)? Is there a way to target a specific one? Thanks, Joe -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.

Hello, I have been having problems installing the Login Engine. I follow all the steps found on the download site (rails-engines.org), but when I get to the DB_SCHEMA step, I do rake engine_migrate ENGINE=login in the application root. """ C:\rails\cag> rake engine_migrate ENGINE=login (in C:/rails/cag) rake aborted! Don''t know how to build task