Doctrine Project

[DCOM-68] Add @codeCoverageIgnoreStart and @codeCoverageIgnoreEnd to annotation ignore map

Sun, 25 Sep 2011 14:36:26 +0000

Add @codeCoverageIgnoreStart and @codeCoverageIgnoreEnd to annotation ignore map

[DCOM-62] Github-PR-53 by shawndellysse: ArrayCollection#join

Wed, 14 Sep 2011 16:54:17 +0000

This issue is created automatically through a Github pull request on behalf of

{username}

Url: https://github.com/doctrine/common/pull/53

Message:

Added the `join` method to `ArrayCollection`.

[DCOM-57] Doctrine\Common\Cache\AbstractCache::deleteAll() does not take the namespace into account

Thu, 8 Sep 2011 17:16:21 +0000

The deleteAll() function delete all keys with no respect of the namespace.

Using orm:clear-cache:metadata with memcache result in the deletion of all memcache keys. (including keys unrelated to the orm)

[DCOM-47] When using different class loaders

Tue, 27 Dec 2011 23:21:04 +0000

ClassLoader::classExists($class); will fail if different class loader is used which does not return any boolean value. This includes Symfony2 UniversalClassLoader

I have never used this function before because native PHP method class_exits($class, true) first will try to autoload. But if the class does not exist
and you are using Doctrine\Common::ClassLoader and you call class_exists($class) it will trigger fatal error. This behavior makes it impossible to make code compatible
with different class loading mechanisms for Doctrine2

[DCOM-40] Using shared references with the SharedFixtureInterface with the DataFixtures extension will not work.

Wed, 14 Sep 2011 16:48:36 +0000

I did not know where to issue that component, but since this extension using the Doctrine Common namespace I thought it relevant to issue the bug here.

Consider the following shared fixures (as stated on jwage's github repo here: https://github.com/doctrine/data-fixtures)

In case if fixture objects have relations to other fixtures, it is now possible to easily add a reference to that object by name and later reference it to form a relation. Here is an example fixtures for Role and User relation

namespace MyDataFixtures;

use Doctrine\Common\DataFixtures\AbstractFixture;

class LoadUserRoleData extends AbstractFixture
{
    public function load($manager)
    {
        $adminRole = new Role();
        $adminRole->setName('admin');

        $anonymousRole = new Role;
        $anonymousRole->setName('anonymous');

        $manager->persist($adminRole);
        $manager->persist($anonymousRole);
        $manager->flush();

        // store reference to admin role for User relation to Role
        $this->addReference('admin-role', $adminRole);
    }
}

namespace MyDataFixtures;

use Doctrine\Common\DataFixtures\AbstractFixture;

class LoadUserData extends AbstractFixture
{
    public function load($manager)
    {
        $user = new User();
        $user->setUsername('jwage');
        $user->setPassword('test');
        $user->setRole(
            $this->getReference('admin-role') // load the stored reference
        );

        $manager->persist($user);
        $manager->flush();

        // store reference of admin-user for other Fixtures
        $this->addReference('admin-user', $user);
    }
}

This will not use the last reference as a MANAGED entity but whether as a NEW one since the manager gets cleared (thus the unit of work) on each call to load() for the AbstractExecutor and thus marking any new references to the 'admin-user' considered a NEW entity, which should not be the case.

The current workaround is to directly fetch the entity using the EM's find() function, but that completely eliminates the main goal SharedFixtures' references are bringing.

I have provided the small patch that adress this issue, tests still pass.

[DCOM-37] orm:convert-d1-schema not working

Wed, 14 Sep 2011 16:32:11 +0000

orm:convert-d1-schema ~/schema.yml yml ~/newyml returns The helper "em" is not defined