TYPO3.Flow

If you define a uniqueConstraints in a Model you want to have that checked as soon as the add() method of your repository is called. If you don't do that it might lead into some problems later in your controller.

For example you have the following model:

/**
 * @scope prototype
 * @entity
 * @Table(name="acme_demo_domain_model_mymodel", uniqueConstraints={@UniqueConstraint(name="name_idx", columns={"name"})})
 */
class MyModel {
    /**
     * @var string
     */
    protected $name;

    [snip]
}

The propety name has a doctrine unique contraints which means that i can only exists once in the database.

Now you have this controller

class AcmeDemoCommandController extends \TYPO3\FLOW3\MVC\Controller\CommandController {

    /**
     * Add a MyModel
     *
     * Adds a MyModql with a given name
     *
     * @param string $name The name of the repository
     * 
     * @return void
     */
    public function addCommand($name) {
        try {
            $newModelInstance = new \Acme\Demo\Domain\Model\MyModel($name);
            $this->MyModelRepository->add($newModelInstance);
        } catch (\Exception $e) {
            $this->outputLine('The MyModel could not be created!');
            return -1;
        }

        $this->outputLine('New MyModel was created.');
    }

}

On the command line you do the following:

./flow3 AcmeDemo:add foo

This works the first time as expected.

When you execute it the second time, you get an Exception because the name "foo" is already present in the database. You get the Exception even though you put the code in a try catch blog is, this is because the method to actually save the changes is called after your code. The responsible method is persistAll().

This leads to some more problem which I put into a seperate issue. For now let me tell you that it doesn't work.

It would be really cool if the add would return something that tells me if an object can be persisted or not. Otherwise I had to check all my DB constraints manually whenever I work with my model. And if I understood DDD corectly, this is not the Domain of my controller. ;-)