similar to: now that I have migrations working (I think I do anyway)

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

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

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

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

Having a weird issue where I can migration to version 1, but then go no further, and cannot go back to 0 -- but only from the command line. If I open up script/console I can do migrations just fine - down to 0 or up to 2, via ActiveRecord::Migrator. So I know the migrations must be valid, and I can verify that tables are created or destroyed in the database. Does anyone have any idea why this

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

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

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, 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):

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

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

We have a scenario where we have a core engine with module add-ons. What modules that will be used differ from deployment to deployment. Each of these modules might need different things in the db (both structure and data) and I want each module to be in charge of its own db structure. Each module is contained in its own source directory and what modules to use is determined in the build

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ok, so rake migrate --trace gets you this: Khavi:~/Documents/WebCode/rails/clickcaster sgoodwin$ rake migrate -- trace (in /Users/sgoodwin/Documents/WebCode/rails/clickcaster) ** Invoke migrate (first_time) ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:migrate ** Execute migrate then it

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I am a new developer at www.clickcaster.com and we''re having some trouble with migrations. When I tried to run the migrations on our database (which previously hadn''t used migrations), nothing happens, it stops before it runs any of the migrations. However, when I try

(I know ''version'' is the only field, but in case this changed one day my question will still apply) ;) I had to drop all my tables to re-run my migrations from version 1. When I executed ''rake db:migrate'' everything ran successfully. Which puts my database ''state'' at migration 007_xxx. Now when I add a migration (008_xxx) and re-run

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 ?

Is there some standard way to test migrations? It seems to me that an additional safeguard for migrations would be to test and see if applying the migrations to the test database allows one to reconstruct the structure of the development database. If you can''t, then there is an error in your migrations, most likely because someone hand-modified the database without generating a

Ok, so now Users need to be associated with Organizations. I''ve created a migration and added a ''organization_id'' column to the users table. I want the default organization_id to be the first Organization. So I have :default => Organization.find(:first). But it''s complaining about not being able to find the constant ''Organization''. Any

Just got an odd error running migrations off of a new trunk today. Is this my fault is there a bug right now? > rake db:migrate --trace (in /home/magneticworld) ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment rake aborted! undefined method `instantiate_observers'' for ActiveRecord::Base:Class

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