search for: schema_migr

Why would, in an upgrade from 3.0.1 to 3.0.3, a rake db:migrate run this: SELECT "schema_migrations"."version" FROM "schema_migrations" vs this ? SELECT `schema_migrations`.`version` FROM `schema_migrations` __ rake db:migrate output __ rake aborted! Mysql::Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version...

Hi all! How can I change the name of the schema_migrations table? I have to do this because I can only use one database but want to have several rails projects. I hope this is possible at all. greets flo schaf -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are su...

...tural modifications, and thus did not need to run any migrations. However, the deployment scripts by default include command cap deploy:migrations. Instead of recognizing that there were no new migrations, Rails wanted to start over and run all migrations. The schema_info table was there, but no schema_migrations table. When was the schema_info table supposed to be replaced with a schema_migrations table; shouldn''t it have happened automatically? Should I now go in and delete the schema_info table and manually create and populate a schema_migrations table? -- Posted via http://www.ruby-for...

...t; part, once I run " rake RAILS_ENV=production db:migrate --trace", it shows the following errors: (in /usr/share/puppet-dashboard) > rake aborted! > Mysql::Error: CREATE command denied to user ''dashboard''@''localhost'' for > table ''schema_migrations'': CREATE TABLE `schema_migrations` (`version` > varchar(255) NOT NULL) ENGINE=InnoDB > /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:227:in > `log'' > /usr/share/puppet-dashboard/vendor/rails/acti...

Hi, after changing a primary key column name, the auto-increment information (MySQL) and sequence (Oracle) are lost. What is the correct way to rename primary keys? Thanks, Gustavo -- 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

I''ve created a table in a SQL Server database using a migration, successfully. I''ve tried to change the name of a column in the table and got the error message above when running ''rake db:migrate''. Previously I have developed using MySQL and Sqlite and migrations have worked successfully. This is an error I have not seen before. Has anybody seen this and worked

...::MysqlAdapter:0xb6fc6f50 @logger=#<ActiveSupport::BufferedLogger:0xb70935f0 @log=#<File:/home/grant/stuff/ruby/rails/auction-demo-mysql/log/development.log>, @no_block=false, @auto_flushing=1, @buffer=[], @level=0>, @runtime=0.134179830551147, @quoted_column_names={"unique_schema_migrations"=>"`unique_schema_migrations`", "schema_migrations"=>"`schema_migrations`", "id"=>"`id`", "auctions"=>"`auctions`", :version=>"`version`", :title=>"`title`"}, @connection=#&l...

...::MysqlAdapter:0xb6fc6f50 @logger=#<ActiveSupport::BufferedLogger:0xb70935f0 @log=#<File:/home/grant/stuff/ruby/rails/auction-demo-mysql/log/development.log>, @no_block=false, @auto_flushing=1, @buffer=[], @level=0>, @runtime=0.134179830551147, @quoted_column_names={"unique_schema_migrations"=>"`unique_schema_migrations`", "schema_migrations"=>"`schema_migrations`", "id"=>"`id`", "auctions"=>"`auctions`", :version=>"`version`", :title=>"`title`"}, @connection=#&l...

...ive would be a new rake task: db:migrate:all that would run the lower-numbered versions that would otherwise be skipped. I know there is a potential for confusion, but I don''t think that confusion is any worse than now with some migrations never being run. 2. Include the contents of schema_migrations in schema.rb The current approach for db:schema:load is to assume that all migrations in db/migrate up to the :version option have been run. This is fraught with peril. Given the issue in #1 above, it''s possible to assume some skipped migrations have been run, which could...

...04033 AddCommentRangeToUser: migrated (0.0000s) =================== If I do the same command again it does EXACTLY the same three migrations. (Of course, they were all throwing errors, since they had already done the migration once, so now the lines that do anything are commented out.) The table schema_migrations has 147 rows, with the last three being 20090301004033 20090222224734 20090217193953 over and over. It''s like it gets lost and can''t find what one it did last. Is there some way to say, "Dump all that migration data, assume everything has been migrated in to t...

...oduction environment and the initial DB migration ran fine and the application works as expected. A couple of days ago I created another migration and it worked fine on my dev environment, but in the production environment it comes back with the error: rake aborted! PGError: ERROR: relation "schema_migrations" already exists : CREATE TABLE "schema_migrations" ("version" character varying(255) NOT NULL) It seems to think that it needs to switch the project over to the new migration tables again. Has anyone come across this before and have any ideas how to fix it? Thanks,...

We recently upgraded to Rails 2.1. When dumping the schema ( rake db:schema:database) from our database I expected to see the command to create the schema_migration table. Why is this table not in the schema dump file ? Also, the schema_version is still in the file, but not in the database ?

...9;t any migration for another 3 migrations whereas sometimes ago when I run a migration with rake db:migrate, all my migrations are migrated. ---------- 4 - After I type rake db:migrate and after that Rake execute "create_football_leagues.rb" I go to mysql and I saw a table with "schema_migrations" name. and in that table there are some versions of my migrations. now I want to know what is the application of such a table ? ---------- 5 - In http://guides.rubyonrails.org I read that if we want to change the primary key of a table from default id to our own field we must use :pr...

...g my first Rails website (OS X Snow Leopard, TextMate) and decided to switch from sqlite to mysql. After many-many hours of searching the internet I managed to install mysql gem. Now I get this error when I try to run rake migrations: rake aborted! Mysql::Error: query: not connected: CREATE TABLE `schema_migrations` (`version` varchar(255) NOT NULL) ENGINE=InnoDB I read somewhere that new latest Rails doesn''t work with mysql properly and I have to reinstall mysql etc etc. I am seriously tired of this, it just doesn''t make any sense. I can set up Apache+PHP+MySQL environment literary...

...ig ** Execute db:migrate rake aborted! NoMethodError: undefined method `to_a'' for #<SQLite3::Statement:0x9d6a2dc>: SELECT name FROM sqlite_master WHERE type = ''table'' AND NOT name = ''sqlite_sequence'' AND name = "schema_migrations" /var/lib/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/sqlite_adapter.rb:248:in `block in exec_query'' /var/lib/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract_adapter.rb:280:in `block in log'' /var/lib/gems/...

I''m trying to run " rake db:migrate " and im getting an error back: ------------------------------------------------------------------------ C:\wamp\www\demoproject>rake db:migrate (in C:/wamp/www/demoproject) rake aborted! Mysql::Error: query: not connected: CREATE TABLE `schema_migrations` (`version` varchar(255) NOT NULL) ENGINE=InnoDB (See full trace by running task with --trace) ------------------------------------------------------------------------ Something is definitely wrong because when I try to run " script/dbconsole " i get an error also --------------...

...WEBrick 1.3.1 [2013-10-28 20:55:15] INFO ruby 1.9.3 (2013-02-22) [x86_64-darwin10.8.0] [2013-10-28 20:55:15] INFO WEBrick::HTTPServer#start: pid=654 port=3000 Started GET "/" for 127.0.0.1 at 2013-10-28 20:55:37 -0700 *ActiveRecord::SchemaMigration Load (0.1ms)* *SELECT "schema_migrations".* FROM "schema_migrations"* ActiveRecord::PendingMigrationError (Migrations are pending; run ''rake db:migrate RAILS_ENV=development'' to resolve this issue.): activerecord (4.0.0) lib/active_record/migration.rb:379:in `check_pending!'' active...

..., I''d appreciate any help I can get, thank you: -------------- Error ------------- ruby 1.8.6 (2009-08-04 patchlevel 383) [i386-mingw32] C:\Ruby\projects\music_library>rake db:migrate (in C:/Ruby/projects/music_library) rake aborted! Mysql::Error: query: not connected: CREATE TABLE `schema_migrations` (`version` varchar(255) NOT NULL) ENGINE=InnoDB (See full trace by running task with --trace) C:/Ruby/bin/rake:19: [BUG] Segmentation fault ruby 1.8.6 (2009-08-04) [i386-mingw32] This application has requested the Runtime to terminate it in an unusual way. Please contact the application...

Hi, I have added to my migration a change_table action. It works fine on my local dev machine, but on the production server the migration does not happen although the schema.rb file gets correctly updated. I am running Rails 2.1.1 -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google

Howdy, I''m having some trouble migrating. From a fresh db, rake db:migrate runs successfully, with no errors. The tasks in the latest migration are performed with no problem. However, the latest version # is not saved in the schema_migrations table. All other version numbers are. Subsequent rake db:migrate cause errors because columns/tables already exist. I''ve tried changing version numbers on the latest migration file and even commenting out all of the logic, with no luck. Has anyone seen this before? Any ideas? Man...