title: Rake Unit Testing : "False" being used for column "no"
body: <h1>Post :: Model</h1>
  
  <pre><code>class Post &lt; ActiveRecord::Base
    attr_accessible :body, :name, :no, :num
  end
  </code></pre>
  
  <h1>Posts.yml  under (test/fixtures/)</h1>
  
  <pre><code>one:
    name: MyString
    body: MyString
    no: 1
    num: 2
  </code></pre>
  
  <p>On running, <code>rake test:units</code>, the following stack trace is generated</p>
  
  <pre><code>Error:
  test_Post_for_correct_attributes(PostTest):
  ActiveRecord::StatementInvalid: SQLite3::SQLException: table posts has no column named false: INSERT INTO "posts" ("name", "body", "false", "num", "created_at", "updated_at", "id") VALUES ('MyString', 'MyString', 1, 2, '2012-12-26 10:24:36', '2012-12-26 10:24:36', 980190962)
  </code></pre>
  
  <p>Now, here - the table field 'no' has been converted to 'false'. (which seems to be a problem since its being interpreted as FALSE and not as a object variable)</p>
  
  <p>A bug with how it is converting the variables from yaml to object?</p>
  
  <p>Rails version <code>Rails 3.2.9</code> and Ruby <code>ruby 1.9.3p194</code></p>