@@ -1,6 +1,6 @@ spec = Gem::Specification.new do |s| s.name = "fixture_dependencies" - s.version = "1.2.1" + s.version = "1.2.2" s.author = "Jeremy Evans" s.email = "code@jeremyevans.net" s.platform = Gem::Platform::RUBY fixture_dependencies.gemspec @@ -135,6 +135,7 @@ class << FixtureDependencies # return if object has already been loaded into the database if existing_obj = model_method(:model_find_by_pk, mtype, model, attributes[model.primary_key.to_sym]) puts "#{spaces}using #{record}: already in database" if verbose > 2 + loading.pop return existing_obj end obj = model.new lib/fixture_dependencies.rb 5d4464beac9d2b03f4f81a113d5fd66c53a87e92 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/fixture_dependencies/commit/3566588c5aee5fe075e8d7eb5beecc84fedeff5f 3566588c5aee5fe075e8d7eb5beecc84fedeff5f 2009-05-07T16:00:24-07:00 2009-05-07T16:00:24-07:00 Fix issue where an association cycle is detected incorrectly, bump version to 1.2.2 This is a one line change that pops the loading stack when the object already exists in the database, so if later on the object needs to be loaded again, it won't detect a cycle (since there is no cycle). 793691d22f6469e8a6c146e4ab84565dcb107a01 Jeremy Evans code@jeremyevans.net