has_one maintains the association with separate after_create/after_update

This way parent models can get their own after_create and
after_update callbacks fired after has_one has done its job.

1 files changed, 8 insertions, 0 deletions

diff --git a/activerecord/test/schema/schema.rb b/activerecord/test/schema/schema.rb
index ea62833d81..fe59d8aeec 100644
--- a/activerecord/test/schema/schema.rb
+++ b/activerecord/test/schema/schema.rb
@@ -156,6 +156,11 @@ ActiveRecord::Schema.define do
     t.integer :company_id
   end
 
+  create_table :iris, :force => true do |t|
+    t.integer :eye
+    t.string  :color
+  end
+
   create_table :customers, :force => true do |t|
     t.string  :name
     t.integer :balance, :default => 0
@@ -194,6 +199,9 @@ ActiveRecord::Schema.define do
     t.integer :car_id
   end
 
+  create_table :eyes, :force => true do |t|
+  end
+
   create_table :tyres, :force => true do |t|
     t.integer :car_id
   end