# Functional testing strangeness with rake

**URL:** <https://www.ruby-forum.com/t/functional-testing-strangeness-with-rake/90426>\
**Category:** Ruby\
**Created:** [March 28, 2007, 6:05pm UTC](https://www.ruby-forum.com/t/functional-testing-strangeness-with-rake/90426 "2007-03-28T18:05:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![scorintha](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/278dde/32.png) [@scorintha](https://www.ruby-forum.com/u/scorintha)\
**Post date:** [March 28, 2007, 6:05pm UTC](https://www.ruby-forum.com/t/functional-testing-strangeness-with-rake/90426/1 "2007-03-28T18:05:55Z")

</div>

Hi,

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  
…

end

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.