<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -1,4 +1,4 @@
-Copyright (c) 2007 Flawed Logic, OG Consulting, Rick Bradley &lt;rick@rickbradley.com&gt;
+Copyright (c) 2007 Flawed Logic, OG Consulting, Rick Bradley, Yossef Mendelssohn
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the</diff>
      <filename>MIT-LICENSE</filename>
    </modified>
    <modified>
      <diff>@@ -1,5 +1,5 @@
 = Object Daddy
-&lt;b&gt;Version 0.0.1 (Nov 25, 2007)&lt;/b&gt;
+&lt;b&gt;Version 0.2.2 (May 13, 2008)&lt;/b&gt;
 
 Author::	Rick Bradley (mailto:blogicx@rickbradley.com), Yossef Mendelssohn (ymendel@pobox.com)
 Copyright::	Copyright (c) 2007, Flawed Logic, OG Consulting, Rick Bradley, Yossef Mendelssohn
@@ -9,20 +9,20 @@ Object Daddy is a library (as well as a Ruby on Rails plugin) designed to
 assist in automating testing of large collections of objects, especially webs
 of ActiveRecord models. It is a descendant of the &quot;Object Mother&quot; pattern for
 creating objects for testing, and is related to the concept of an object
-Exemplar or &quot;stereotype&quot;.
+exemplar or &quot;stereotype&quot;.
 
 WARNING: This code is very much at an &quot;alpha&quot; development stage. Usage, APIs,
 etc., are all subject to change.
 
-TODO: put linkage into b.logi.cx post about the history.
+See http://b.logi.cx/2007/11/26/object-daddy for inspiration, historical drama, and too much reading.
 
 == Installation
 
-Unpack the object_daddy directory into vendor/rails/ in your rails project.
-Run the object_daddy/install.rb Ruby script. A definitive public revision
-control access point is forthcoming that will make it possible to install the
-plugin via script/plugin install, which will automatically run the
-installation hook.
+1. Unpack the object_daddy directory into vendor/rails/ in your rails project.
+2. Run the object_daddy/install.rb Ruby script.
+
+A. Or, as an alternative and assuming your script/plugin has git support, 
+   script/plugin install git://github.com/flogic/object_daddy.git
 
 == Testing
 
@@ -203,6 +203,28 @@ class User &lt; ActiveRecord::Base
   generator_for :age =&gt; 25
 end
 
+
+Required belongs_to associations are automatically generated when generating an instance,
+but only if necessary.
+
+class Category &lt; ActiveRecord::Base
+  has_many :items
+end
+
+class Item &lt; ActiveRecord::Base
+  belongs_to :category
+  validates_presence_of :category
+end
+
+Item.generate will generate a new category, but some_category.items.generate will not.
+Unless, of course, you are foolish enough to define a generator in the exemplar.
+
+class Item
+  generator_for(:category) { Category.generate }
+end
+
+Once again, don't do that.
+
 === Rails 'surprises'
 
 Due to the way Rails handles associations, cascading generations (as a result of</diff>
      <filename>README</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>d47787ef7fa1e06b9483f43663ba9930db1e4027</id>
    </parent>
  </parents>
  <author>
    <name>Yossef Mendelssohn</name>
    <email>ymendel@pobox.com</email>
  </author>
  <url>http://github.com/flogic/object_daddy/commit/1660e8a4f030bb845e4f1b4c1b6ca39c660e3ab2</url>
  <id>1660e8a4f030bb845e4f1b4c1b6ca39c660e3ab2</id>
  <committed-date>2008-05-13T09:47:05-07:00</committed-date>
  <authored-date>2008-05-13T09:47:05-07:00</authored-date>
  <message>Updating README, version, &amp;c.</message>
  <tree>1f672e603fe7b001dae04bfc6521fc3fcbb3833a</tree>
  <committer>
    <name>Yossef Mendelssohn</name>
    <email>ymendel@pobox.com</email>
  </committer>
</commit>
