similar to: Schema Dump

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

Do I now define database changes directly in db/migration/0001_add_a_new_table file ? Obviously the point is not to make the changes directly in postgresql db anymore right? Thanks Craig

I have tables with double as their field''s datatype. When I ran db:schema:dump, Rails changed all of these double to float. I would like to know why, and if there is anyway I could preserve the datatype. Thanks a lot, Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk"

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

I haven''t seen anyone mention this yet. The tail end of the migration process is a call to schema.dump. Our primary keys are uuids and these choke schema.dump on both oracle and postgres. The latter fails silently (skips three tables) while the former complains about the RAW(16) in each of the three tables. Anyone had a similar experience? -- Posted via http://www.ruby-forum.com/.

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:

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

Like lots of other folks, I''ve been searching for a way to scratch my fixture itches. Rathole is my extraction of a few techniques we''ve successfully applied at my day job. We''ve been using Rathole for a month or so now, but I''d really like some feedback from a wider audience. Rathole tackles: * Conflicting PK''s (no more id''s in fixture

All, It looks like rake db:schema:dump does not dump primary keys. I have some legacy table that don''t follow the convention ie pk = id and none of the primary keys for these tables are getting dumped... Seems strange as this should be readily available from the db. I am using MySQL. Is anybody else seeing that ? Incidentally how does one specify a primary key using

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

I''ve created a table in a SQL Server database using a migration, successfully. I''ve tried to change the name of a column in the table and got the error message above when running ''rake db:migrate''. Previously I have developed using MySQL and Sqlite and migrations have worked successfully. This is an error I have not seen before. Has anybody seen this and worked

As of some recent version of Postgres, plpgsql is created for new databases by default, but the sql schema export (config.active_record.schema_format = :sql) expots a create command in development_structure.sql, resulting in an error. CREATE PROCEDURAL LANGUAGE plpgsql; I could not find the version this changed in, however it is noted here:

Hey there, I''ve adjusted some of my many to many join tables recently to use a composite primary key based on the id''s in the two columns - instead of using a surrogate key. I just did a db:schema:dump, and it looks something like this: create_table "class_members", :id => false, :force => true do |t| t.integer "user_id", :default => 0,

Hi there! I am PHP developer and trying to learn ROR. Currently I am building my first Rails website (OS X Snow Leopard, TextMate) and decided to switch from sqlite to mysql. After many-many hours of searching the internet I managed to install mysql gem. Now I get this error when I try to run rake migrations: rake aborted! Mysql::Error: query: not connected: CREATE TABLE `schema_migrations`

Hey, looks pretty messy out here the last two days...so please let me know if this is known, or if you can confirm. Just upped to Rails 1.1. When I run `rake test` I get: rake aborted! ./db/schema.rb:17: parse error, unexpected kEND ./db/schema.rb:21: parse error, unexpected $, expecting kEND (See full trace by running task with --trace) Uggly. In schema.rb: t.column

Hi, Everything is in the title. With Rails 2.3.4 and MySQL 5.0.41: If have a table like this: +----------------+------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +----------------+------------+------+-----+---------+----------------+ | id | int(11) | NO | PRI | NULL |

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 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, I''m trying to get my head around using migrations to define my initial schema. When using migrations, I want to: - Avoid creating a new migration for every small change. Limit it to one migration per checkin. - When creating a new (fresh) schema, I do not want to go through the overhead of all the migrations. These are the steps I came up with, to create the initial schema: 1.