similar to: Issue with version field in schema_info

I have the rails recipes book and i was going through the migrations recipe. Everything seemed to work except for the last part in trying to do a rake migrate with a migration file version 1 and the schema_info version set to 0. Without the force attribute, the rake migration fails, as expected. So the recipe says to run this: ruby script/runner

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

Is anyone using migrations with a SQL Server database who might be able to lend me a hand? I''ve used migrations with MySql in the past and haven''t run into any issues so forgive When I run rake migrate nothing is actually getting updated in my database. I created a migration using ./script/generate migration AddFooTable and updated the migration to look as follows: class

Hi all, Sorry for another newbie question! I''ve got a legacy firebird database which I wish to use, and thanks to help from this group I''ve used Dr Nic''s Magic Models to get RoR talking to the database. However, I wish to create a new table ("reports") in this database, and so generated the scaffold such that the file "db/migrate/

On a rails app that I''m developing I converted a regular old .sql file into a rails migration. Since I generated the migration in my development environment, it created the schema_info table for me. However, when I updated my production environment and tried running rake migrate it complained that schema_info doesn''t exist. Is there a rake task for getting around this yet, or

Posting to merb list in case it is a merb problem. (?!??) The error still happens with sequel 0.2.1. ---------- Forwarded message ---------- From: Kevin Williams <kevwil at gmail.com> Date: Sep 23, 2007 10:26 AM Subject: error with schema_info when doing multiple migrations To: sequel-talk at googlegroups.com I tried to post an issue to the project site but it kept giving me 500 server

Hi all, I am facing a problem while using rails "migrate" feature for creating tables in a database. Following are the details. I have 2 applications say "app1" & "app2". I want both of them to use same database say "testdb". For "app1", I create 3 models which in turn create 3 migration files with prefix, 001_, 002_ & 003_. Now I

of course, now that I am relying upon migrations, I''m at a loss to explain why it isn''t working. I have a system which has production and development and I have a development system at home where I created all the new code and migrations. I committed my changes via svn and used ''svn update'' to update the live system. I started by running the migration on the

Hello, I get this error trying to load some data from DB. I''m using Rails 1.2.2 on Fedora Core 6 and Sybase adapter. This worked fine when application run under Rails 1.1.6 but now I''m migrating to 1.2.2 and have some problems. At browser I got: SQL Command for table_structure for tplib_bckps failed Message: schema_info not found. Specify owner.objectname or use sp_help to

Hi all, I''m having a very odd problem with db:migrate. I''m using Rails 1.2.5 on Windows XP SP2 and Ruby 1.8.6 I have seven migrations. If I run them with an empty database, it runs the first three, then halts. When I look in schema_info, the version is 3. If I run db:migrate VERSION=7, then it runs through the remaining 4 migrations, and the version is 7 in the DB.

Hi, When doing a ''rake migrate'', schema_info is not updated (it does not contain any row). Migration is done properly the first time, but fails the second time I run it, since there is no info in schema_info. I am running rails 1.1.2, using script/generate migration to generate the migration file. Any help? Thank you. Jean-Etienne http://www.novAgora.hu -- Posted via

Running rails 1.1 and MySQL 5 on Kubuntu. I moved the same rails project from one machine to another. To set up the database I try to run `rake migrate` but I am greeted with the error/stack trace below. Any idea why this could be? It doesn''t seem to be a permissions problem--I can login to the database as my application just fine. I tried downgrading MySQL to v4.1 because that is

Hi all, I''m confused about how migrations work. I''ve been using them for a couple of weeks but haven''t had any serious rollback issues yet. Just now I added a field to a table with a migration and ran "rake migrate", which added the field as expected. This was in the file db/migrate/007_mymigration.rb, making it version 7. Later I changed my mind and

Has anyone encountered this error or know how to correct it? I couldn''t find any Rails-specific info about this on google. Here are the circumstances: /usr/local/bin/ruby --version ruby 1.8.4 (2005-12-24) [i686-linux] /usr/local/bin/rails --version Rails 1.1.6 ## Create mcd app rails mcd -d oracle cd mcd ## Create oracle tablespace & user sqlplus ''/ as

Hi all, Rails 1.1.4 Rake 0.7.1 PostgreSQL 8.1.4 Windows XP Pro I checked for errata on pragmaticprogrammer.com, but didn''t see any explicit mention of this issue. I''m going over the depot example in AWDwR, 2nd ed, and I can''t get the migration to work on p. 82. Specifically, the AddTestData example (with reduced description text to save my fingers some typing):

I''m working on a plugin which needs to add both schema and data to the app database, and I''m trying to figure out the best way to do it. I''d like to use a db migration to modify the schema and load the data from a YAML fixture, but Rails doesn''t seem to support migrations for plugins. To do so, the schema_info table would need to change to include a

Hi, my company uses only 1 database for all the developments, so it is a big problem for using migrations in Rails because of the schema_info table. How can I solve this problem? Is there a way to change the schema_info table name? Thanks. Nicolas. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are

with a simple table def. class Objects < ActiveRecord::Migration def self.up create_table :objects do |table| table.column :name, string end def self.down drop_table :objects end end when I run rake migrate, I get: ** Invoke migrate (first_time) ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:migrate rake

Just going through ''agile web development with rails'' 2nd ed. I accidentally created an empty migration source file with the wrong name, ruby script/generate migration add_test_date and then straight after that created the one I wanted to use ruby script/generate migration add_test_data and populated the second one - when I ran rake db:migrate a few times it did not seem

My migrations were working fine until today. I dropped and re-created the database.But, when I go to apply my migrations, rake migrate aborts with this error. You have a nil object when you didn''t expect it! You might have expected an instance of Array. The error occured while evaluating nil.first Any idea what might be wrong? The migrations look right. It''s talking to the