similar to: Re: rake db:migrate throws unexpected error

Displaying 20 results from an estimated 20000 matches similar to: "Re: rake db:migrate throws unexpected error"

2008 Jun 09
0
Error when executing "rake db:migrate" with frozen Rails 2.1.0 on Media Temple
I''m hoping someone might have some insight into this, because I don''t quite know how to figure this one out. I''m running the command with Capistrano''s deploy:migrate to my (mt) Media Temple (gs) Grid Server, but I get the same error (from "rake aborted!" and on below) when I run "rake db:migrate" directly on the server in the
2013 Jun 29
0
rake db:create giving undefined method `' for nil:NilClass
My ruby version is 1.8.7 I have installed mysql-essential-5.0.90-win32 and using Fedena 2.3.5 List of all gems installed:* columnize (0.3.6) declarative_authorization (0.5.1) fattr (2.2.1) ffi (1.9.0) gem_plugin (0.2.3) highline (1.6.19) i18n (0.4.2) metaclass (0.0.1) mime-types (1.23) mocha (0.14.0) mongrel (1.1.5) mysql (2.8.1) net-ping (1.6.0) prawn (0.6.3) prawn-core (0.6.3) prawn-format
2011 Nov 01
1
rake db:migrate aborted
I''m reading the rails tutorial book and in chapter 6 page 199 I have to make a rake db:migrate, but I get this error: rake aborted! undefined method `prerequisites'' for nil:NilClass (See full trace by running task with --trace) When I try with rake db:migrate --trace I get the following errors: rake aborted! undefined method `prerequisites'' for nil:NilClass
2013 Feb 01
0
rake db:migrate failing against oracle
Hello All -- I am using jruby 1.6.7.2 with rails 3.2.11 to create a brown bag for several other developers. I cannot get the migration to work to save my life... In my database yaml file I have the following: --- development: adapter: jdbc driver: oracle.jdbc.driver.OracleDriver url: jdbc:oracle:thin:@localhost:1521:xe username: brownbag password: brownbag pool: 500 --- When I run:
2006 Jul 25
3
create production tables? use "rake db:migrate"?
Hi, What is the normal mechanism for creating the tables in the (a) test and (b) production databases. For example the following didn''t work for creating the production tables: a) change environment.rb to include "ENV[''RAILS_ENV''] ||= ''production''" b) run "rake db:migrate" However this seemed to still work against DEV not
2008 Jan 31
0
Rake Bug? db:create:all directs db:migrate to the test db..
Dear all, task ''test'' do Rake::Task[''db:create:all''].invoke Rake::Task[''db:migrate''].invoke end Did I miss something or what? Turns out that this simple task would have migration done in the test db. I''ve tried to "puts RAILS_ENV" inbetween and it shows "development", but migration''s still done in
2013 Oct 29
3
rake db:migrate debacle
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]
2007 Dec 26
2
How to set environment when calling rake task inside another
This is what I have inside a rake task. In this rake task I need to call another rake task called email:send_messages. However I need to pass the RAILS_ENV as ''staging''. Rake::Task["rake:email:send_messages"].invoke I tried a lot of variations but none of them work. Rake::Task["rake:email:send_messages"].invoke RAILS_ENV=staging
2013 May 07
4
Rake db:migrate
Hello, I''m trying to use command rake db:migrate, but in MySQL I continuous get an empty set and I do know why. #/db/seeds.rb User.create(username: "lorenz", password: "mypass", admin: true) When I run: rake db:seed RAILS_ENV=development --trace I received: ** Invoke db:seed (first_time) ** Execute db:seed ** Invoke db:abort_if_pending_migrations (first_time) **
2007 Jun 23
7
rake db:migrate strange behaviour "wrong number of arguments (1 for 0)"
Hi everybody, May be somebody has a clue, why I get these errors below, while trying to migrate. Any help is very appreciated! Greetinx Rafael I was trying to experiment a litte bit with redMine (www.redmine.org). But I can only install it locally. On a system with already a mongrel_cluster running, I get strange errors, already while trying to start the migration rake db:migrate
2006 Aug 08
6
rake migrate the first time - uses more than schema_info?
All, I have two migration files, file 1 and file 2. For reasons that I don''t want to go into unless I must, I want to only run file 2 on my production database (file 1 contains a bunch of table creation stuff for already existing tables). I figured if I created a schema_info table and set the version in it to 1, then I could just run rake db:migrate RAILS_ENV=production and just
2012 Jun 22
0
rake db:seed on EC2
Hey guys, How would one run the equivalent of rake db:seed on their EC2 instance? I added this to my deploy.rb file: namespace :deploy do desc "Populates the Production Database" task :seed do puts "\n\n=== Populating the Production Database! ===\n\n" run "cd #{current_path}; rake db:seed RAILS_ENV=production" end end But when running cap
2006 Jul 05
10
rake migrate RAILS_ENV="production"
On the wiki it says to migrate your DB to production, you can run: rake migrate RAILS_ENV="production" This is taken from: http://wiki.rubyonrails.com/rails/pages/UnderstandingMigrations My database is set up with correct MySQL permissions granted and the database.yml is pointing at it. I get no errors when I run it, but equally my production database does not change at all.
2006 Oct 10
4
rake migrate -- which db affected?
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.
2006 Jul 25
7
Problem running rake db:migrate
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
2011 Apr 20
6
rake db:create fails
Hello folks, I´m here trying to find the way to solve my problem. When i try to run rake db:create or rake db:create:all the process stops and the databases are not created. I change the directives, putting --trace before the rake db:create and the steps are C:\appws\cookbook>rake db:create --trace (in C:/appws/cookbook) ** Invoke db:create (first_time) ** Invoke db:load_config (first_time)
2013 May 14
4
rake precompile:assets throwing error
While running rake precompile:assets i''m getting the following error This is the error message: rake assets:precompile:all RAILS_ENV=production rake aborted! undefined local variable or method `establish_connection'' for ActiveRecord::Base:Class Please help -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To
2010 Feb 27
1
Cannot migrate DB due to "getaddrinfo: Name or service not known"
I am using Rails 2.2.2 and try to do a DB migration, but got the following error. I am using Centos 5.4. Can someone give me a clue? >> rake db:migrate RAILS_ENV="production" rake aborted! getaddrinfo: Name or service not known (See full trace by running task with --trace) [current]$ rake db:migrate RAILS_ENV="production" --trace ** Invoke db:migrate (first_time) **
2006 Jul 23
18
help with "rake db:migrate" error please?
Hi, Just trying to get my first database based rails app up on dreamhost.com. The app was working prior to putting in mysql DB usage but I''m just stuck on getting the app working with mysql. I''ve already created the database and can connect to it manually. Below is the error I get after running the rake migrate. It worked OK on my home PC environment. I did change the
2010 Nov 30
2
db migration fails
I''m deploying new rails applications. Everything works well except when it comes to the db migration: * executing "cd /var/rails/benefits_test/releases/20101129190121 && /opt/ruby-enterprise-1.8.7-2010.02/bin/rake RAILS_ENV=production db:util:migrate" servers: ["ps-test-app1"] [ps-test-app1] executing command ** [out :: ps-test-app1] (in