"Diego Carrion" <[email protected]> wrote in message
news:[email protected]...
Yes, it exists in belongs_to already.
It doesn't exists in has_one.
I added the option to has_many because I really needed it, I prefer to add
>functionalities on demand.
Adding functionality on demand is a great way to write applications. It is
the basis of TDD and BDD. But it does not work quite as well for frameworks
in my opinion.
For a framework to work well it should be consistant. I should be able to
guess functionaility based on what I already know, rather than having to
look it up. Rails generally does quite well with that.
If you think it will be useful to implement the option in has_one and
>has_and_belongs_to_many associations, I can do it without problems :)
I would like it, but I am a nobody, just a regular rails user, so don't
assume my stances are shared by the core team.
My thoughts are that here it would be inconsistant to not implement it on
all 3 has_* associations. My gut tells me that there is nothing special
about the has_many case that would justify only it having this feature.
--
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.
