I am setting this up, in this way, so that we have some extensibility. We may wish to have some sort of a polymorphic association where multiple models need to have a scheduling model available to them. That being said, as of right now, only the pto model needs it so I am doing a belong_to and has_one association between the two

2013-05-27 13:09:33 -04:00
parent 8bfdf45ff9
commit 21752fab7e
7 changed files with 79 additions and 1 deletions
@@ -0,0 +1,17 @@
+# Read about fixtures at http://api.rubyonrails.org/classes/ActiveRecord/Fixtures.html
+
+one:
+  event_type: MyString
+  date_begin: 2013-05-27
+  date_end: 2013-05-27
+  event_name: MyString
+  event_desc: MyString
+  user_id: 1
+
+two:
+  event_type: MyString
+  date_begin: 2013-05-27
+  date_end: 2013-05-27
+  event_name: MyString
+  event_desc: MyString
+  user_id: 1