similar to: Migrations that don''t affect schema_info.version?

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

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

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

(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

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/

Does anyone have MySQL replication set up for a Rails App that uses migrations? I''m having an issue where every time I run a migration Rails is trying to create the schema_info table. Mysql::Error: Table ''schema_info'' already exists: CREATE TABLE schema_info (version int(11)) This causes a problem on the slave databases where the replicated create table statement

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

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

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

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, a Javascript in one of my Rails templates needs to load a static XML file. I tried several places to put the actual XML file, and I also tried to make the file a rails template (tried both .rhtml and .rxml) and access it via a controller action. None of these ways worked. Does the lighttpd server know how to serve XML files, or do I need to configure it first? Or, is there a good workaround?

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

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 read in various places that although migrations aren''t transactional, all you need to do is wrap you migration method in "ActiveRecord:: Base.connection.transaction do" to make the self.up or self.down transactional. In my experience (Rails + PostgreSQL), this doesn''t work very well. If my migration hits an exception, any tables that were touched remain modified.

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

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, does anybody know of any good HowTo for consuming XML-RPC and/or SOAP web services in Rails? I found some for Ruby (via soap4r/xmlrpc4r), but I was wondering whether there is something built into Rails already. So far it looks like there are methods to create web services, but not to consume them. Ingo Weiss