similar to: some love for migrations

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 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 ## I have 6 simple and fundamental Problem in RoR migration and although I googled it and read many article about it and research it for a week , I didn''t understand it. please help me for these problems : ---------- 1 - When I create a model (for example "rails generate model Football_League") , I see in db/migration a "create_football_leagues.rb" . I want

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

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

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

Hi, we internally are creating gems out of particular sets of models, both to share them among multiple Rails apps, but also to use them within background scripts. If possible, I''d like for the models to function with ActiveRecord/ ActiveSupport as the only dependencies and not require a full Rails environment. This is for the purposes of our background jobs which use the same set of

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]

I''m trying to create several large applications that share 60-80 percent of their functionality. I''d like to find some way to abstract the common functionality into a gem, plugin, or engine which I can then deploy as many times as needed for each application. The catch is each app will definitely need that 20% extra functionality and it may include changes or enhancements to

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.

Greetings, I''m trying to convert a HABTM w/attributes join table in my database into a join model table in order to utilize the new has_many :through functionality introduced in Rails 1.1. Here''s the current table definition: licenses_user_groups: license_id, user_group_id, usage_notes Perhaps it was a mistake, but I made (license_id, user_group_id) the primary key. Now,

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

Hi, I started writing a project using Rails 1.x, then moved to 2.0 a couple of weeks after it came out. This moved the project to the new migration structure (timestamp based), and everything''s worked fine on my development environment. I''ve since done the initial deployment of the project to my production environment and the initial DB migration ran fine and the application

Hello all, I''ve been trying to get ruby on rails to work with my local install of mysql(its with wamp). Windows XP, Ruby 1.8.6, rails 2.3.5, rubygems 1.3.5, mysql 5.2 something I believe. I have ruby installed in: C:\Ruby and my mysql is installed in: C:\wamp\bin\mysql\mysql5.1.30\bin I''ve attempted to change my database.yml file to include the port 80, and port 3036, the