DataMapper ORM v1.8.2

[eluser]tarciozemel[/eluser]
[quote author="WanWizard" date="1333465363"]I'll reply here as it may benefit others.

A quick scan of your code doesn't really reveal anything obvious.

What could happen: if you save an object with relations, Datamapper will first save the object itself. It will then check if related objects are passed, and if so, it will save these objects too, before creating the relation. This save with call the save() method on these objects.

In case this fails (for example because of validation rules that fail), the save and relate operation is aborted, but the return code is ignored. Which could cause your save() to return TRUE, even if related saves returned FALSE.

Can you validate if this is the case by making sure the two objects in $relations are saved (and check their status) before trying to save the object itself? If this is the issue, then you've found a bug.[/quote]

So, unfortunately, it's a bug.

In the code I send you with the error, the save part is:

Code:

$relationships = array
(
    'authentication' => $this->authentication
    ,'company'       => $company
);

if ( ! $this->save($relationships))
{
    // stuff
}

When I use like this, the relation happens!

Code:

// Saved BEFORE!
$this->authentication->save();
$company->save();

$relationships = array
(
    'authentication' => $this->authentication
    ,'company'       => $company
);

if ( ! $this->save($relationships))
{
    // stuff
}

That's it. Eager to the bug fix release! :cheese:

Best regards, WanWizard!