[dev] RDO Mapper update patch

[Duck]

On Tuesday 06 June 2006 03:10, Chuck Hagenbuch wrote:
> This isn't intended usage - if the $object is an RDO instance the
> assumed use case is that either you're calling $rdo_instance->update()
> which is calling the mapper internally, or you've already updated the
> rdo object before calling the mapper object yourself. What use case do
> you have for interacting directly with the mapper this way?
>
> (Also, the patch allows bypassing any validation done in the RDO
> object's __set method - also a problem when you just pass in an id
> directly, but no need to compound that.)

So I should first call RDO::setFields() then RDO_Mapper::update().
But even this dosen't work.
The id being set in mapper update is results always null. (line 214)

In the RDO examples I don't find a working usage. 
Maybe an relationships example will be good to.

Duck