Comments for Awesomism http://awesomism.co.uk Think... Believe... Create... Release! Fri, 04 Sep 2009 10:55:46 +0000 hourly 1 http://wordpress.org/?v=3.1 Comment on Symfony 1.2, Doctrine 1.1 and saving relationships by gunzip http://awesomism.co.uk/2009/05/19/symfony-12-doctrine-12-and-saving-relationships/comment-page-1/#comment-5 gunzip Fri, 04 Sep 2009 10:55:46 +0000 http://awesomism.co.uk/?p=20#comment-5 if you're creating a new object the methods link/unlink cannot work like that because you don't have any "id" to connect to yet (at least with Doctrine < 1.1). You must call the doSave method <b>before</b> using them: <code> public function doSave($con = null) { parent::doSave($con); $this->getObject()->unlink('FaqGroups'); $this->getObject()->link('FaqGroups', $this->getValue('faq_groups_list')); } </code> I think this is fixed in Doctrine >= 1.1 because link/unlink methods don't change the object save() is called. Symfony 1.2 ships with the 1.0 one though. if you’re creating a new object the methods link/unlink cannot work like that because you don’t have any “id” to connect to yet (at least with Doctrine < 1.1). You must call the doSave method before using them:


public function doSave($con = null)
{
parent::doSave($con);
$this->getObject()->unlink('FaqGroups');
$this->getObject()->link('FaqGroups', $this->getValue('faq_groups_list'));
}

I think this is fixed in Doctrine >= 1.1 because link/unlink methods don’t change the object save() is called. Symfony 1.2 ships with the 1.0 one though.

]]> Comment on Symfony 1.2, Doctrine 1.1 and saving relationships by blt http://awesomism.co.uk/2009/05/19/symfony-12-doctrine-12-and-saving-relationships/comment-page-1/#comment-4 blt Tue, 02 Jun 2009 14:07:59 +0000 http://awesomism.co.uk/?p=20#comment-4 You might also want to look at my post on <a href="http://www.brandonturner.net/blog/2009/05/doctrine11-with-symfony12/" rel="nofollow">using Doctrine 1.1 with Symfony 1.2</a>. Doctrine 1.1 changes a few things relating to how relationships are saved. If you use Symfony generated forms this can become problematic. You might also want to look at my post on using Doctrine 1.1 with Symfony 1.2. Doctrine 1.1 changes a few things relating to how relationships are saved. If you use Symfony generated forms this can become problematic.

]]>