Hi all,

There is something confusing with has_many in the current API :
When deleting a record with association.delete, the corresponding
association's foreign key is nullified. However, if has_many has
the :dependent option set (to any value), the association's destroy
method is called instead.
This is awfully inconsistent with the behavior expected when
setting :dependent to :nullify.

While browsing the Trac database, I found several patches submitted to
address this issue :
http://dev.rubyonrails.org/ticket/5209 (1 year old !)
http://dev.rubyonrails.org/ticket/7309
These patches look good to me, but still haven't been applied. Is
there any good reason for this ?
If not, it would be nice if someone could take care of this ;)


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" 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-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to