similar to: 6 fundamental migration problems for beginners

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 subscribed to the Google Groups "Ruby on

I have a semi-grand plan for some changes to migrations. Mostly this is motivated by the upcoming 3.0 release and wanting to get migrations in engines working. 1. Don''t skip migrations with version numbers lower than "current". I only recently tripped over this, but apparently it''s been this way since 2.1 when we got timestamps masquerading as large/sparse

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

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 suspect this is because it is a 1.x application which was upgraded, but my migrations don''t "stick." If I Coder-iMac:patton colin$ rake db:migrate (in /Users/colin/Desktop/patton) == 20090217193953 AddLastYearToTarget: migrating ============================== == 20090217193953 AddLastYearToTarget: migrated (0.0001s) ===================== == 20090222192059 AddEditorToUser:

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 there! I am PHP developer and trying to learn ROR. Currently I am building 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`

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

Hi all, I am in the process of adding Migration support to the Ingres ActiveRecord adapter and have run in to a problem. During the call to create_table the Ingres adapter some how causes ruby to blow the stack and coredump/segv. I have tracked down the problem down to "add_column_options!" in "lib/active_record/connection_adapters/abstract/schema_statements.rb".

Hi all, I am in the process of adding Migration support to the Ingres ActiveRecord adapter and have run in to a problem. During the call to create_table the Ingres adapter some how causes ruby to blow the stack and coredump/segv. I have tracked down the problem down to "add_column_options!" in "lib/active_record/connection_adapters/abstract/schema_statements.rb".

Hi Puppet Users group, I have followed the guide to the puppet-dashboard DB "Preparing Schema" 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

So I have the models class FootballGame < ActiveRecord::Base end and class Team < ActiveRecord::Base end I want to be able to do something like this @t1 = Team.create(:name=>"Michigan Wolverines football") @t1.save @t2 = Team.create(:name=>"Penn State Nittany Lions football") @t2.save @g = FootballGame.create(:hometeam => @t1, :awayteam => @t2) @g.save

Hello All, I''m happy to announce the next stable release of Foreman, main new features include: - Integration of Puppet Reports, once enabled you would see a real time overview of all of yours hosts status. - Improved support for multiple Puppet Masters (e.g. import facts and reports from remote serves over http) - Simplified migration from existing external nodes setup,

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 ==================================================== --

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

Hi - We''ve got a Rails application/Oracle database that we just upgraded from Rails 1.2 to 2.3.2 We did not have any database structural 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.

Hi! First of all, this is my first application on Rails, and i''m stuck at a migration. i created a demo app (the demo_app from michael hartl''s tutorial) as usual: rails new demo_app, rails generate scaffold User name:string email:string, and when i do rake db:migrate, this stack appears: rake db:migrate --trace ** Invoke db:migrate (first_time) ** Invoke environment

XLSolutions Corporation (www.xlsolutions-corp.com) is proud to announce: (1) Introduction to R/S+ programming: Microarrays Analysis and Bioconductor *** San Francisco / July 17-18, 2006 *** *** Chicago / July 24-25, 2006 *** *** Baltimore / July 27-28, 2006 *** *** Raleigh / July 17-18, 2006 *** ***

Hi, when I define a db column to be non-nullable or of length 20 or as numeric, I would expect rails to validate that, but that doesn''t seem to be the case. Any idea why that is? The metadata is accessible, at least in the mysql case. I am using rails 1.0 with mysql 5. Cheers, Mariano

I think I am pissing into the wind to make migrations work at this point. Looking at http://wiki.rubyonrails.org/rails/pages/UnderstandingMigrations it appears that the problem that I am having is that postgresql can''t do the drop_table part because of the foreign_key keys (constraints) which requires ''cascade'' as an option to drop some of the tables that have other