I don't think that is intended. mapValue() doesn't mean you can set the
value then.
- Jon
On Thu, Nov 20, 2008 at 9:50 AM, Sebastian <[EMAIL PROTECTED]>wrote:
>
> Maybe I should mention that the second line works perfectly well and
> prints "0815". The third line then _crashes_.
>
> $player->map
Maybe I should mention that the second line works perfectly well and
prints "0815". The third line then _crashes_.
$player->mapValue('password_confirmation', '0815');
print $player->password_confirmation;
$player->password_confirmation = '1234';
--~--~-~--~~~---~--~---
Sorry, my answer was total bogus.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email t
> Shouldn't you use this?
> $player->setPasswordConfirmation('1234');
Should it? Regarding the Doctrine documentation _set() and _get()
should come into action. However: Setting the value by explicitly
calling set() doesn't work, too. Same for $player
['password_confirmation'].
I'm a bit helples
Shouldn't you use this?
$player->setPasswordConfirmation('1234');
- Jan
On 20 Nov., 16:12, Sebastian <[EMAIL PROTECTED]> wrote:
> Hi.
>
> I need some help - again ;) .
>
> In a unit test I'm doing something like this:
>
> $player->mapValue('password_confirmation', '0815');
> print $player->pas
