If that patch could get some +1's all should be fine.
On 26 Jun 2008, at 16:02, Jean-Baptiste Escoyez wrote:
>
>> So the new validate option might be a workaround or fix, but it
>> looks like I'm going to have to move to edge rails to get that., and
>> hope for Rails 2.1.1 to be released soon.
>
> So the new validate option might be a workaround or fix, but it
> looks like I'm going to have to move to edge rails to get that., and
> hope for Rails 2.1.1 to be released soon.
Indeed, it might be. Though you have to append ':validate => false' to
every 'has_many' in your app.
And be c
On Thu, Jun 26, 2008 at 6:55 AM, Jean-Baptiste Escoyez <[EMAIL PROTECTED]>
wrote:
>
> I experienced exactly the same problem and I think it is an important
> issue.
>
Thanks so much for the reply. I worked a bit last night just before leaving
work on Jan De Poorter's suggestion of writing a tes
I experienced exactly the same problem and I think it is an important
issue.
It comes from the fact that associated objects are validate twice in
Rails 2.1 : First when parent is not saved yet and a second time when
parent is saved (I don't understand this behaviour).
Here is the result of a qui
Could you reproduce this behaviour in a test? That would facilitate
tracking down the problem for all of us.
thanks,
Jan De Poorter
On 26 Jun 2008, at 00:03, Rick DeNatale wrote:
> I think that this is more appropriate for rails-core than the
> general list.
>
> I've been doing a lot of fru
