similar to: problems with migrations in sql server

development.log contains quite a few SELECTS on system tables like COLUMNS. Wouldn''t it be more efficient to cache this info? I''m also wondering about strings like "[4;35;1m". What''s their purpose and is it possible to get rid of them? They look like screen coordinates and makes no sense in a text file. Christer Processing ReportController#create (for

I am unable to get ActiveRecord session support to work under 2.x against a SQL Server database. I''m starting to wonder if anyone is running 2.x against SQL Server? Is anyone running under the following configuration: Rails 2.x SQL Server 2000 DB (using AR adapter in ODBC mode) AR store for ActionController session store. I''d like to chat with you if you are. Thanks, Wes --

Hello, I have rails using a MSSQL db. The set up works fine with low volume, but with 2+ requests/second I keep on getting the following error: DBI::DatabaseError: Execute OLE error code:80004005 in Microsoft OLE DB Provider for SQL Server Cannot create new connection because in manual or distributed transaction mode. HRESULT error code:0x80020009 Exception occurred.: SELECT

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

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

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

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

All, Database: SQL Server 2000 SQLServer adapter in ODBC mode I have a Capistrano deploy script which fails when I run against my production DB. Apparently, this is the because the user that is set up for production has "guest" privileges in my SQL Server database and when Capistrano runs, instead of looking at the dbo.schema_info table (which has the correct version # - yes 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

(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

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

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

We have installed rails 1.1.2 and Ruby 1.8.4 on solaris. When we attempt to run the initial migration we get the following error: Mysql::Error: Lost connection to MySQL server during query: SELECT version FROM schema_info /web/server/pkgs/ruby-1.8.4/lib/ruby/gems/1.8/gems/activerecord-1.14.2/lib/active_record/connection_adapters/abstract_adapter.rb:120:in `log''

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

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

When trying to migrate my db using rake I get the following error message: rake aborted! No migration with version number 3 I am using sqlite3 as my database server. Any help is much appreciated. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email