Forum: Ruby functional testing strangeness with rake

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Mark N. (Guest)
on 2007-03-28 20:05

I have a Rails 1.2.3 app that's running under cruisecontrol.rb (thanks
Thoughtworks). I recently added a test to a search controller that makes
a fulltext query to a MySQL table. The create_table statement in the
migration clearly indicates that the engine should be MyISAM:

 create_table "events", :options => 'TYPE=MyISAM', :force => true do |t|
      t.column "url_hash", :string, :limit => 30
      t.column "user_id", :integer
      t.column "active", :boolean, :default => true, :null => false
      t.column "featured", :boolean
      t.column "start_time", :datetime
      t.column "end_time", :datetime


Whenever I blow the database away and run rake db:migrate in the
development environment, the tables are created with the MyISAM engine.
However, whenever I run rake db:migrate in the test environment, all
tables in that db are InnoDB, except schema_info.  Does anyone have any
clues on why this behavior would be different? Thanks.
This topic is locked and can not be replied to.