[Deprecated] DMZ 1.5.3 (DataMapper OverZealous Edition)

[eluser]mcnux[/eluser]
[quote author="OverZealous.com" date="1247290063"]mcnux

There are two solutions to your problem.

1) Since you are remapping the client to a different user, the easiest solution is to simply save the clients to the new user. Because each client can only be related to one user (both by rule AND by database design), the new $userTwo->id will be set in $client->user_id. You will still need to load the new Clients on the new User ($userTwo->client->get()) to see the update.
[/quote]

I thought saving the clients to the new user is what I was trying to do in the following?

Code:

$userOne = new User();
$userOne->get_by_id($id);

// $userTwo = new User(); // whoops, this should show loading another user, see next line
$userTwo = new User($idTwo);
$userTwo->save($userOne->client->get()->all);

But this does not have any affect - the user_id remains that of $userOne. If there is another method I should be using, please advise.

Also, the old user will still have the related set in memory for this HTTP request (meaning, $userOne->client->all will still contain a reference). There is no way for DM to know that you are moving clients from one user to another, due to PHP garbage collection limitations.

Yes I am aware of this, and am checking the database directly.

2) $userOne->delete($client) requires that $client->user_id be able to be stored as NULL. When you set FK rules in most databases, you often need to explicitly allow NULLs, as is mentioned in the docs (under Rules). Please read over your database's docs, and make sure that your rules are not preventing the column from being set as NULL.

Yes I have set the user_id field on clients to allow NULLs. I am able to remove the relationship (set the user_id to NULL) when I delete $userOne, the problem is I don't want to delete the user, I just want to reallocate his clients to another user.

You seem to think I am missing something and this should be working, so hopefully I am doing something stupid. I would appreciate an example of achieving your first solution as I thought I was trying exactly what you suggested