From 071373857dddeefcb7a36f8838c03c5e88dd6e20 Mon Sep 17 00:00:00 2001 From: schneems Date: Mon, 2 Jun 2014 10:42:48 -0500 Subject: [ci skip] explain association behavior. When you manually specify `id:` attribute in a fixture Rails' built in association assignment feature will no longer work. http://stackoverflow.com/questions/23985675/incorrect-association-in-fixtures This commit raises awareness of this behavior and encourages developers to look directly at the fixture documentation. --- guides/source/testing.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/guides/source/testing.md b/guides/source/testing.md index 9468f03442..c01b2e575a 100644 --- a/guides/source/testing.md +++ b/guides/source/testing.md @@ -96,6 +96,12 @@ one: category: about ``` +Note: For associations to reference one another by name, you cannot specify the `id:` + attribute on the fixtures. Rails will auto assign a primary key to be consistent between + runs. If you manually specify an `id:` attribute, this behavior will not work. For more + information on this assocation behavior please read the + [fixture api documentation](http://api.rubyonrails.org/classes/ActiveRecord/FixtureSet.html). + #### ERB'in It Up ERB allows you to embed Ruby code within templates. The YAML fixture format is pre-processed with ERB when Rails loads fixtures. This allows you to use Ruby to help you generate some sample data. For example, the following code generates a thousand users: -- cgit v1.2.3