README.rdoc in secondbase-0.2.0 vs README.rdoc in secondbase-0.3.0

@@ -21,14 +21,16 @@
 
 
 == Installation
 Modify your Gemfile to include Secondbase:
   
-  gem 'secondbase', '0.1.0'
+  gem 'secondbase', '0.3.0'
 
-Run `bundle install`.  You thought it would be harder?
+Run `bundle install`.  You thought it would be harder?  If you're using Rails 2.x, then yes, a little bit harder.  You must also add this to your Rakefile:
 
+  require 'secondbase/tasks'
+
 == Usage
 === Database
 Configure your database.yml to define your secondbase:
 
   # Your normal rails definitions...
@@ -111,11 +113,9 @@
 This is patch to fixtures that will identify the fixtures which belong to models that extend SecondBase::Base.  The patch will then ensure that the table descendants of SecondBase::Base get loaded into your second test (data)base.
 
 At this time, there is not support for anything other than fixtures (i.e. factories).  If you have the time to update this gem to be test object compatible, by all means...
 
 == TODO
-- We should support Rails 2.x as well as 3.x 
-
 - Migration generator needs support for attribute generation (similar to rails generate migration).  For example:
   `rails generate secondbase_migration AddTitleBodyToPost title:string body:text published:boolean`
 
 - rake db:fixtures:load is currently broken.  Like many other things I have fixed, it assumes you only one a single database and attempts to load all fixtures into it.  I don't believe we can get away with alias chaining this one, I think (like the Fixtures class), we'll have to freedom patch it.