similar to: Migration error after upgrading project to Rails 2.0

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

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:

I''m writing some code that accesses some lagacy database on PostgreSQL. Since the old database had some really ughly and weird naming conventions (like CamelCase). To work around this I created a second schema (named rails) in the same database and gave the tables and fields some rails-friendly names. The database user that Rails uses has its search_path set to the rails schema. That way

Hi, I get errors doing this: 1) createdb myapp_test 2) rake db:test:clone_structure 3) rake test:units rake aborted! PGError: ERROR: relation "matches" already exists I''m using the :sql schema format because there are some problems with postgres and the :ruby schema format config.active_record.schema_format = :sql It seems rake test:units is trying to create the tables

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.

This might be a problem with postgresql, but I''m not sure. In a migration I have renamed a table so I wanted to rename a sequencer as well. It looks like: execute "ALTER TABLE global_vacations_id_seq RENAME TO vacations_id_seq;" execute "ALTER TABLE vacations ALTER COLUMN id SET DEFAULT nextval(''vacations_id_seq''::regclass);" But the process of

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

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:

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

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

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 all. I have has_and_belongs_to_many association between models: Section and Content. class Section < ActiveRecord::Base acts_as_tree has_and_belongs_to_many :contents belongs_to :default_content, :class_name => ''Content'', :foreign_key => ''default_content_id'', :dependent => :nullify end class Content < ActiveRecord::Base belongs_to

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

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 have a specific need to ''fixate'' my ''roles'' table sequence when migrating. at migration #4, I have 28 records in my roles tables and I can manually reset the roles_id_seq but it stands to reason that since I am doing everything else in the migration, I might as well reset the sequence there too. so I tried this in my migration file... execute

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

Hey, I''ve googled this pretty thoroughly and saw a couple people with the same issue but none of the solutions worked for me. Background: I am trying to upload my Radiant CMS site to Heroku. Location: http://morning-frost-41.heroku.com/ Problem: Well on Heroku, the thing that really stands out it: PGError: ERROR: relation "pages" does not exist Pages refers to a table within

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 everyone, I''m new in rails. After I ran "gem update --system", I had a lot of problems when running rails projects. I tried to fix from error to error and now when I run rails project, it occurs error like this: About your application’s environment PGError in Rails/infoController#properties could not connect to server: No such file or directory Is the server running