On Apr 30, 6:46 pm, Greg Willits <[email protected]>
wrote:
> (Rails 2.3.2, OS X 10.5, MySQL 5.0.x)
>
> I have combed through all my callbacks, even commented them out. Nothing
> in there appears to be the problem (nothing forcing a save that I can
> see).
>
"Adding an object to a collection (has_many or
has_and_belongs_to_many) automatically saves that object, except if
the parent object (the owner of the collection) is not yet stored in
the database" (http://api.rubyonrails.org/classes/ActiveRecord/
Associations/ClassMethods.html)
Fred
> I have this short loop code inside a dead-simple controller index method
> with no other code that could interfere AFAICT.
>
> This seems too obvious to be a Rails bug, so I am assuming it's my code
> somehow, somewhere.
>
> Any ideas on what else to look at?
>
> -- gw
> --
> Posted viahttp://www.ruby-forum.com/.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
