Doctrine Project

[DDC-633] fetch="EAGER" is not loading one to one associations

Tue, 28 Sep 2010 15:19:25 +0000

<?php
namespace vo;

/**
 * @Entity
 */

class Appointment {
	
    /** @Id @Column(type="integer") @GeneratedValue(strategy="IDENTITY") */
    public $id;
	
	/**
     * @OneToOne(targetEntity="Patient", inversedBy="appointment", fetch="EAGER")
	 * @JoinColumn(name="patient_id", referencedColumnName="id")
     */
	public $patient;
	
}

When doing a findAll() on appointments, $patient is being created as a proxy even though fetch is EAGER.

[DDC-790] Generating entities with cli failed on inheritated entities due missing PK

Thu, 16 Sep 2010 05:32:46 +0000

While generating entities with:

./doctrine orm:generate-entities --generate-methods=true ../tmp/entities

getting MappingException: No identifier/primary key specified for Entity 'Entities\Admin'. Every Entity must have an identifier/primary key.

Admin is class inheritated, definition included:

Person: http://pastebin.com/5r9fXrAu
Admin: http://pastebin.com/51BcRZWZ

[DDC-522] Join columns can not be named the same as the association fields.

Dependency — Wed, 15 Sep 2010 14:05:18 +0000

Join columns can currently not be named the same as the association fields in a class. This apparently causes Doctrine to insert the identifier of the associated object instead of the actual object (on hydration of the fetch-joined association at least).

Example:

    /**
     * @OneToOne(...)
     * @JoinColumn(name="item", referencedColumnName="id")
     */
    private $item;

[DDC-765] \Symfony\Components renamed to \Symfony\Component (singular) ... refactoring unfinished. console cannot be invoked

Mon, 30 Aug 2010 22:55:13 +0000

I pulled from github the whole thing, but still stuck with sandbox:

\doctrine\tools\sandbox>php doctrine.php
.PHP Warning: require(doctrine\lib\vendor\Symfony\Components\Console\Helper\Helper.php): failed to open st
ream: No such file or directory in C:\Inetpub\wwwroot\BugTrackerORM\doctrine\lib\vendor\doctrine-common\lib\Doctrine\Common\ClassLoader.php
on line 148
PHP Stack trace:
PHP 1.

{main}

() ..... doctrine\tools\sandbox\doctrine.php:0
PHP 2. require() .... doctrine\tools\sandbox\doctrine.php:21
PHP 3. Doctrine\Common\ClassLoader->loadClass() ... doctrine\lib\vendor\doctrine-common\lib\Doctrine\Common\C
lassLoader.php:0
PHP 4. require() ... doctrine\lib\vendor\doctrine-common\lib\Doctrine\Common\ClassLoader.php:148
PHP 5. Doctrine\Common\ClassLoader->loadClass() C:\Inetpub\wwwroot\BugTrackerORM\doctrine\lib\vendor\doctrine-common\lib\Doctrine\Common\C
lassLoader.php:0

Warning: require(.... doctrine\lib\vendor\Symfony\Components\Console\Helper\Helper.php): failed to open stream:
No such file or directory in.... doctrine\lib\vendor\doctrine-common\lib\Doctrine\Common\ClassLoader.php on lin
e 148

well, it seams that at some stage Symfony\Components got renamed to Symfony\Coponet:

$ git log Component
commit 4a9f36800e3f55bc2cf61033573e1103594b4742
Author: S<C3><A9>bastien HOUZE <sebastienhouze@mbash.livebox.home>
Date: Mon Aug 23 08:21:41 2010 +0200
Symfony/Components renamed into Symfony/Component

When I copied Component into Componets I got:
.PHP Fatal error: Cannot redeclare class Symfony\Component\Console\Helper\Helper in doctrine\lib\vendor\Sy
mfony\Components\Console\Helper\Helper.php on line 21

[DDC-684] Flaw in Build Process?

Mon, 30 Aug 2010 17:39:18 +0000

As I see it from our build script, each PEAR package of ORM and DBAL includes the Common sources again, although it sets itself as dependent on that package? That would mean the ORM package overwrites the files from the DBAL and Common packages.

[DDC-778] Query Clone Removes DQL

Mon, 30 Aug 2010 14:30:24 +0000

The fix for ~~DDC-770~~ made the \Doctrine\ORM\AbstractQuery call the free method when __cloned. This is fine with an abstract query but when you clone from a Doctrine\ORM\Query it calls the free method of that class which nulls out the DQL statement. This breaks the example given in the Doctrine ORM cookbook of writing a custom walker.

This is either a bug in the documentation or a bug in Doctrine ORM.

[DDC-771] EntityGenerator generates wrong use statement in entity file

Sat, 28 Aug 2010 11:01:05 +0000

If I use EntityGenerator with class to extend 'Extension\\Doctrine\\ORM\\ActiveEntity
ActiveEntity' in generated files I have this use statement:

use Extension\Doctrine\ORM\ActiveEntity;

class XXX extends ActiveEntity

and php ends with error. I think the use statement should look like:

use Extension\Doctrine\ORM\ActiveEntity\ActiveEntity;

class XXX extends ActiveEntity

After I repaired this function it works ok:

private function _getClassToExtendNamespace()
{
    $refl = new \ReflectionClass($this->_getClassToExtend());

    return $refl->getNamespaceName() ? $refl->getNamespaceName():$refl->getShortName();
}

return $refl->getNamespaceName() ? $refl->getNamespaceName().'\\'.$refl->getShortName():$refl->getShortName();

I'am not sure if it is bug or I am doing something wrong.

[DDC-752] Postpone Metadata Validation Until After Driver and loadClassMetadata Has Executed

Sat, 28 Aug 2010 09:34:32 +0000

Right now the metadata drivers throw exceptions if certain metadata is not specified. While this is convenient for letting the user know about errors, it limits the extensibility of the ORM, specifically what you can do in the loadClassMetadata event. It also means that there is duplicated code in each of the driver implementations for validation.

All validation of the metadata should be postponed until after the metadata driver has executed and also after the loadClassMetadata event has been fired. This way all metadata has been loaded before attempting to validate and the user is still warned about errors. This validation should still be ignored when loading from cache.

Example use case:

Currently, setting a @DiscriminatorMap is required when using inheritance mapping. The loadClassMetadata event provides a way to dynamically set discriminator maps from a config or a database without having to extend a metadata driver.

The specific regression in functionality that this references is MappingException::missingDiscriminatorMap being thrown in the metadata drivers.

[DDC-770] Cleanup Query instance when cloneed

Fri, 27 Aug 2010 15:29:54 +0000

When calling clone $query the instance should be cleaned from parameters.

[DDC-757] Make names for tables and join columns not mandatory

Thu, 26 Aug 2010 13:13:40 +0000

Why is it necessary to specify a name when using the @Table annotation (I guess it's the same using Yaml or XML) when I just want to add some indexes or unique constraints? When I do not specify the @Table at all, the name is generated from the entity's class, why can't it be also generated when I just want to add indexes or uniqueConstraints? My point is why should I write so many same stuff so many times, when Doctrine can already use it's API to do it for me. Preferably I would like to only specify the name when I need to change it from the default, not every time I need to add some explicit indexes The same applies to the @JoinColumn annotation. When I want a nullable=false column, I have (again) specify a name for it, but the generated name would work just fine. Why do I have to specify it by hand?

[DDC-737] Update PersistentCollection to upport slice($offset, $length);

Tue, 24 Aug 2010 15:57:03 +0000

With ~~DCOM-17~~ the Collection interface will be updated to contain one new method, this has to be implemented naively for now:

public function slice($offset, $length = null)
{
    $this->initialize();
    return $this->_col->slice($offset, $length);
}

[DDC-704] Inheritance-type with no discriminator-column results in SQL Error

Mon, 16 Aug 2010 11:10:34 +0000

On an entity (XML mapping atleast) if there is an inheritance-type set but no discriminator-column(s) set the resulting query will have an extra comma at the end of the field list or occasionally (based on inheritance-type) a table alias without a fieldname.

The correct solution would be to throw an exception during the parsing of the mapping that would indicate the inheritance-type is set but no discriminator-columns exist.

[DDC-695] throw error on non-existing relation target column

Thu, 12 Aug 2010 00:36:35 +0000

I had a problem with invalid SQL generated from DQL using JOIN the DQL query was as simple as:

SELECT k, kt FROM Kmz k JOIN k.kmzType kt

the final SQL missed the joined column name:

SELECT k0_.ID_KMZ AS ID_KMZ0, k0_.ID_KMZ_TYPE AS ID_KMZ_TYPE1, k0_.IDENTIFICATOR_HW AS IDENTIFICATOR_HW2, k0_.TIME_INSERT AS TIME_INSERT3, k1_.ID_KMZ_TYPE AS ID_KMZ_TYPE4, k1_.SHORTNAME AS SHORTNAME5, k1_.DESCRIPTION AS DESCRIPTION6, k0_.id_KMZ_TYPE AS id_KMZ_TYPE7 FROM KMZ k0_ INNER JOIN KMZ_TYPE k1_ ON k0_.id_KMZ_TYPE = k1_.

After some time of xdebugging I found that the names in JoinColumn clause in Kmz class annotation were not UPPERCASE as in KmzType - I just got a notice in SQL walker (line 728).

if ($relation->isOwningSide)

{ $quotedTargetColumn = $targetClass->getQuotedColumnName($targetClass->fieldNames[$targetColumn], $this->_platform); // <-- PHP Notice: Undefined index: id_KMZ_TYPE in .../libs/Doctrine/ORM/Query/SqlWalker.php:728 $sql .= $sourceTableAlias . '.' . $sourceColumn . ' = ' . $targetTableAlias . '.' . $quotedTargetColumn; }

else

{ $quotedTargetColumn = $sourceClass->getQuotedColumnName($sourceClass->fieldNames[$targetColumn], $this->_platform); $sql .= $sourceTableAlias . '.' . $quotedTargetColumn . ' = ' . $targetTableAlias . '.' . $sourceColumn; }

I think there might be a check and error thrown in case of missing targetColumn.

[DDC-738] Default Allocation Size remains still 10 in Beta 3

Thu, 12 Aug 2010 00:08:59 +0000

It seems like default allocation size for sequences remains still 10 in Beta 3 - see http://github.com/doctrine/doctrine2/blob/2.0.0-BETA3/lib/Doctrine/ORM/Mapping/ClassMetadataFactory.php - although it should have been already fixed. See also related older ticket - http://www.doctrine-project.org/jira/browse/DDC-577

[DDC-581] Unable to use single value association with IN expression

Wed, 11 Aug 2010 23:18:23 +0000

DQL doesn't allow to use Single Value Association with IN expression.

According to documentation:

InExpression             ::= StateFieldPathExpression ["NOT"] "IN" "(" (InParameter {"," InParameter}* | Subselect) ")"

I think it should be like that:

InExpression             ::= SingleValuedPathExpression ["NOT"] "IN" "(" (InParameter {"," InParameter}* | Subselect) ")"

Suggested solution:
Edit Parser::inExpression method to accept SingleValuedPathExpressions:

    public function InExpression()
    {
        $inExpression = new AST\InExpression( /* Added this: */ $this->SingleValuedPathExpression() );
        ... 
    }

Test case:

$address1 = new \Entities\Address();
$address1->setStreet("Test Street #1");
$em->persist($address1);

$userA = new \Entities\User();
$userA->setName('user A');
$userA->setTest('test A');
$userA->setAddress( $address1 );
$em->persist($userA);

$userB = new \Entities\User();
$userB->setName('user B');
$userB->setTest('test B');
$userB->setAddress( $address1 );
$em->persist($userB);

$em->flush();
$em->clear();


$dql = "SELECT u FROM Entities\User u WHERE u.address IN (SELECT a FROM Entities\Address a WHERE a.street LIKE 'Test Street%' ) ";
$query = $em->createQuery($dql);


$result = $query->getResult();
foreach ($result as $user) {
    echo "<pre>";
    \Doctrine\Common\Util\Debug::dump($user);
    echo "</pre>";
    $em->remove($user);
}

$em->flush();

Without this change It's impossible to select entities having specified association by a subquery with no additional join.

Now this could be done with this DQL:

SELECT u FROM Entities\User u WHERE u.address.id IN (SELECT a.id FROM Entities\Address a WHERE a.street LIKE 'Test Street%' )

But it requires to join addresses table for u.address.id field, which in fact is redundant and ineffective.

_{Tried to find similar issues or feature requests but no results. So I posted it here.}

[DDC-680] Complex Mathematical Expressions in DQL Subselects

Wed, 11 Aug 2010 22:18:42 +0000

It seems complex mathematical expressions are handled differently in DQL Subselects then in normal Selects:

    public function testSelectCorrelatedSubqueryComplexMathematicalExpression()
    {
        $this->assertSqlGeneration(
            'SELECT (SELECT (count(p.phonenumber)+5)*10 FROM Doctrine\Tests\Models\CMS\CmsPhonenumber p JOIN p.user ui WHERE ui.id = u.id) AS c FROM Doctrine\Tests\Models\CMS\CmsUser u',
            'SELECT (SELECT (count(c0_.phonenumber)+5)*10 AS dctrn__1 FROM cms_phonenumbers c0_ INNER JOIN cms_users c1_ ON c0_.user_id = c1_.id WHERE c1_.id = c2_.id) AS sclr0 FROM cms_users c2_'
        );
    }

    public function testSelectComplexMathematicalExpression()
    {
        $this->assertSqlGeneration(
            'SELECT (count(p.phonenumber)+5)*10 FROM Doctrine\Tests\Models\CMS\CmsPhonenumber p JOIN p.user ui WHERE ui.id = ?1',
            'SELECT (count(c0_.phonenumber) + 5) * 10 AS sclr0 FROM cms_phonenumbers c0_ INNER JOIN cms_users c1_ ON c0_.user_id = c1_.id WHERE c1_.id = ?'
        );
    }

Here the first test fails and the second passes. The second has the nested SQL running alone. The failure message is:

1) Doctrine\Tests\ORM\Query\SelectSqlGenerationTest::testSelectCorrelatedSubqueryComplexMathematicalExpression
[Syntax Error] line 0, col 15: Error: Expected One of: MAX, MIN, AVG, SUM, COUNT, got '('

/home/benny/code/php/wsnetbeans/doctrine2/tests/Doctrine/Tests/ORM/Query/SelectSqlGenerationTest.php:31
/home/benny/code/php/wsnetbeans/doctrine2/tests/Doctrine/Tests/ORM/Query/SelectSqlGenerationTest.php:709

[DDC-729] When merging many to many entities back into the repository all associations are deleted on the next flush

Wed, 11 Aug 2010 06:30:50 +0000

When merging a DETACHED entity into the repository with a ManyToMany association, the entries in the join table are deleted on the next flush.

Many Movies have many Artists:

class Movie {
	
	/** @Id @Column(type="integer") @GeneratedValue(strategy="IDENTITY") */
	public $id;
	
	/** @Column(length=50, type="string") */
	public $title;
	
	/** 
	 * @ManyToMany(targetEntity="Artist")
	 */
	public $artists;
	
	public function __construct() {
		$this->artists = new ArrayCollection();
	}
	
}

class Artist {
	
	/** @Id @Column(type="integer") @GeneratedValue(strategy="IDENTITY") */
	public $id;
	
	/** @Column(length=50, type="string") */
	public $name;
	
	/** @ManyToMany(targetEntity="Movie", mappedBy="artists") */
	public $movies;
	
	public function __construct() {
		$this->movies = new ArrayCollection();
	}
	
}

Assume that the database contains:
Movie: id=1, title="Movie 1"
Artist: id=1, name="Artist 1"

and that there is a entry (1, 1) in movie_artist so that there is a many-many relationship between Movie 1 and Artist 1.

I then run the following code to merge the existing associations into the entity manager:

$m1 = new \vo\Movie();
$m1->id = 1;
$m1->title = "Movie 1";

$a1 = new \vo\Artist();
$a1->id = 1;
$a1->name = "Artist 1";

$m1->artists->add($a1); $a1->movies->add($m1);

$m1 = $em->merge($m1);
$m1->artists->set(0, $em->merge($a1));
$a1->movies->set(0, $em->merge($m1));

At this point $m1 should contains merged entities reflecting the same as what is in the database.

If I now run:

$em->flush()

the association is deleted from movie_artist and the SQL log shows DELETE FROM Movie_Artist WHERE Movie_id = '1' as having been run.

Debugging $m1 both before and after the flush shows the expected values, and $em->getUnitOfWork()->computeChangeSets() is empty before the flush.

[DDC-562] @OneToOne is not generating a unique constraint on the owning table

Dependency — Tue, 10 Aug 2010 16:08:25 +0000

Annotations:

<?php

/** @Entity */
class Customer
{
    /**
     * @Id @Column(name="id", type="integer")
     */
    private $customerId;

    /**
     * @OneToOne(targetEntity="Cart", mappedBy="customer")
     */
    private $cart;
}

/** @Entity */
class Cart
{
    /**
     * @Id @Column(name="id", type="integer", nullable=false)
     */
    private $cartId;

    /**
     * Shouldn't unique=true be setting a UNIQUE index on customer_id ??
     *
     * @OneToOne(targetEntity="Customer", inversedBy="cart")
     * @JoinColumn(name="customer_id", referencedColumnName="id", nullable=false, unique=true)
     */
    private $customer;
}

Resulting schema (MySQL), generated with orm:schema-tool:create in CLI:

CREATE TABLE `customer` (
  `id` int(11) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

CREATE TABLE `cart` (
  `id` int(11) NOT NULL,
  `customer_id` int(11) NOT NULL,
  PRIMARY KEY (`id`),
  KEY `customer_id` (`customer_id`),  /* this should be UNIQUE KEY  */
  CONSTRAINT `cart_ibfk_1` FOREIGN KEY (`customer_id`) REFERENCES `customer` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8

I think the key on customer_id in the cart should be generating a UNIQUE KEY by definition on a @OneToOne, with or without the unique= param in the annotation, right?

I've tested this with and without the unique=true param and in both cases it does not generate a UNIQUE key constraint.

[DDC-741] Support SingleValuedAssociationPathExpression owning side Association in InExpression

Tue, 10 Aug 2010 15:08:15 +0000

Title explains everything:

DQL: SELECT v FROM Videos v WHERE v.Venue IN (....)
SQL: SELECT .. FROM ... WHERE v.venue_id IN (...)

[DDC-626] Remove Association Classes

Dependency — Tue, 10 Aug 2010 05:38:36 +0000

The AssociationMapping classes are not needed anymore now that all of the logic has moved to the persisters.

Additionally we get caching benefits doing this and its a dependency for ~~DDC-562~~ (allowing to differ between ManyToOne and OneToOne)

[DDC-728] Inherited (JOINED) associations referred on DQL on owning side doesn't refer to correct table column

Mon, 9 Aug 2010 23:18:40 +0000

Based on code instrospection, it seems that SQL generated is wrong when you attempt to do something like this:

SELECT m FROM CompanyManager m WHERE m.InheritedSingleValuedAssociation = ?1

It seems the column that refers to the association points to wrong table (apparently it points to CompanyManager table).
If everything works, we still need to have coverage to it (we have none).

[DDC-735] PersistentCollection#remove() and PersistentCollection#removeElement() behave differently

Mon, 9 Aug 2010 17:14:42 +0000

It all started when I noticed that removing elements from an a collection using removeElement() didn't actually remove them from the database. While debugging that issue, I found that using remove() worked as expected, so I took a look at ArrayCollection#removeElement() and remove(). I remained thorougly confused for a good 5 minutes because the two methods are virtually identical, yet they were behaving differently. That's when I realized that loading a collection from the database gives you a PersistentCollection, not an ArrayCollection.

So here's the bug: PersistentCollection#remove() and PersistentCollection#removeElement() behave differently. remove() marks the collection as changed only if an element is actually removed, then schedules an OrphanRemoval if applicable. removeElement() unconditionally marks the collection as changed and forgets to check for orphanRemoval.

Since both methods are virtually identical, I suggest that they are refactored to use a common code path instead of duplicating their code. The same should be done with ArrayCollection.

[DDC-584] Document DBAL ArrayType and ObjectType in "Doctrine Mapping Types" instructions

Sun, 8 Aug 2010 13:31:23 +0000

http://www.doctrine-project.org/documentation/manual/2_0/en/basic-mapping#doctrine-mapping-types

Does not mention Doctrine\DBAL\Types\ArrayType or Doctrine\DBAL\Types\ObjectType

Should these be included as documented mapping types?

[DDC-663] Update PEAR install command

Sun, 8 Aug 2010 13:21:58 +0000

Documentation gives incorrect command for downloading ORM from PEAR which causes the installation to fail with the message:

Failed to download doctrine/DoctrineORM, version "2.0.0", latest release is version 2.0.0BETA2, stability "beta", use "channel://pear.doctrine-project.org/DoctrineORM-2.0.0BETA2" to install
install failed

Currently:
sudo pear install pear.doctrine-project.org/DoctrineORM-2.0.0

Change to:
sudo pear install pear.doctrine-project.org/DoctrineORM-2.0.0BETA2

[DDC-651] Bad class (without used namespace) is provided in extends section of entity class declaration in generator.

Sun, 8 Aug 2010 10:44:06 +0000

Bad class (without used namespace) is provided in extends section of entity class declaration in generator.

For example with option --extend="Nette\Object" the class looks like this:

// ...

namespace Entities;

use Nette;

class Foo extends Object <= this is bad. Here should by Nette\Object

// ...

[DDC-703] Explicit change tracking not inherited by inheriting classes

Sun, 8 Aug 2010 10:15:51 +0000

I have a class B that inherits from A using single table inheritance strategy with discriminator column.
On class A I have defined @ChangeTrackingPolicy ("DEFERRED_EXPLICIT"), which should be inherited by B, but it is not currenlty.

This means that when I have a managed instance $b of B $em->getClassMetadata(get_class($b))->isChangeTrackingDeferredExplicit()
does not return TRUE and calling $em->persist($b) and $em->flush() does not save any changes to $b.

If I set @ChangeTrackingPolicy ("DEFERRED_EXPLICIT") on class B it does work. So either way I think B should inherit the change tracking policy of A, or it should have IMPLICT as default like A but not none.

[DDC-542] ManyToMany with Properties sharing Join columns with PRimary Key

Reference — Sun, 8 Aug 2010 09:46:16 +0000

Spagetthi with Tomatoes

Notice: Undefined index: recipe_id in /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/UnitOfWork.php on line 1820

Call Stack:
    0.0005     354964   1. {main}() /home/benny/code/php/wsnetbeans/DoctrineTests/ManyToMany/Recipes.php:0
    0.2063    4308460   2. Doctrine\ORM\PersistentCollection->getIterator() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/PersistentCollection.php:0
    0.2063    4308460   3. Doctrine\ORM\PersistentCollection->_initialize() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/PersistentCollection.php:512
    0.2064    4308460   4. Doctrine\ORM\Mapping\OneToManyMapping->load() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/PersistentCollection.php:210
    0.2064    4308820   5. Doctrine\ORM\Persisters\StandardEntityPersister->loadOneToManyCollection() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/Mapping/OneToManyMapping.php:137
    0.2371    4312216   6. Doctrine\ORM\Persisters\StandardEntityPersister->_createEntity() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/Persisters/StandardEntityPersister.php:559
    0.2372    4312720   7. Doctrine\ORM\UnitOfWork->createEntity() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/Persisters/StandardEntityPersister.php:611


Notice: Undefined index: product_id in /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/UnitOfWork.php on line 1820

Call Stack:
    0.0005     354964   1. {main}() /home/benny/code/php/wsnetbeans/DoctrineTests/ManyToMany/Recipes.php:0
    0.2063    4308460   2. Doctrine\ORM\PersistentCollection->getIterator() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/PersistentCollection.php:0
    0.2063    4308460   3. Doctrine\ORM\PersistentCollection->_initialize() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/PersistentCollection.php:512
    0.2064    4308460   4. Doctrine\ORM\Mapping\OneToManyMapping->load() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/PersistentCollection.php:210
    0.2064    4308820   5. Doctrine\ORM\Persisters\StandardEntityPersister->loadOneToManyCollection() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/Mapping/OneToManyMapping.php:137
    0.2371    4312216   6. Doctrine\ORM\Persisters\StandardEntityPersister->_createEntity() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/Persisters/StandardEntityPersister.php:559
    0.2372    4312720   7. Doctrine\ORM\UnitOfWork->createEntity() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/Persisters/StandardEntityPersister.php:611


Notice: Undefined index: recipe_id in /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/UnitOfWork.php on line 1820

Call Stack:
    0.0005     354964   1. {main}() /home/benny/code/php/wsnetbeans/DoctrineTests/ManyToMany/Recipes.php:0
    0.2063    4308460   2. Doctrine\ORM\PersistentCollection->getIterator() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/PersistentCollection.php:0
    0.2063    4308460   3. Doctrine\ORM\PersistentCollection->_initialize() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/PersistentCollection.php:512
    0.2064    4308460   4. Doctrine\ORM\Mapping\OneToManyMapping->load() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/PersistentCollection.php:210
    0.2064    4308820   5. Doctrine\ORM\Persisters\StandardEntityPersister->loadOneToManyCollection() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/Mapping/OneToManyMapping.php:137
    0.2382    4314316   6. Doctrine\ORM\Persisters\StandardEntityPersister->_createEntity() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/Persisters/StandardEntityPersister.php:559
    0.2383    4314820   7. Doctrine\ORM\UnitOfWork->createEntity() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/Persisters/StandardEntityPersister.php:611


Notice: Undefined index: product_id in /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/UnitOfWork.php on line 1820

Call Stack:
    0.0005     354964   1. {main}() /home/benny/code/php/wsnetbeans/DoctrineTests/ManyToMany/Recipes.php:0
    0.2063    4308460   2. Doctrine\ORM\PersistentCollection->getIterator() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/PersistentCollection.php:0
    0.2063    4308460   3. Doctrine\ORM\PersistentCollection->_initialize() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/PersistentCollection.php:512
    0.2064    4308460   4. Doctrine\ORM\Mapping\OneToManyMapping->load() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/PersistentCollection.php:210
    0.2064    4308820   5. Doctrine\ORM\Persisters\StandardEntityPersister->loadOneToManyCollection() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/Mapping/OneToManyMapping.php:137
    0.2382    4314316   6. Doctrine\ORM\Persisters\StandardEntityPersister->_createEntity() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/Persisters/StandardEntityPersister.php:559
    0.2383    4314820   7. Doctrine\ORM\UnitOfWork->createEntity() /home/benny/code/php/wsnetbeans/doctrine2/lib/Doctrine/ORM/Persisters/StandardEntityPersister.php:611


Notice: Trying to get property of non-object in /home/benny/code/php/wsnetbeans/DoctrineTests/ManyToMany/Recipes.php on line 176

Call Stack:
    0.0005     354964   1. {main}() /home/benny/code/php/wsnetbeans/DoctrineTests/ManyToMany/Recipes.php:0

   100

Notice: Trying to get property of non-object in /home/benny/code/php/wsnetbeans/DoctrineTests/ManyToMany/Recipes.php on line 176

Call Stack:
    0.0005     354964   1. {main}() /home/benny/code/php/wsnetbeans/DoctrineTests/ManyToMany/Recipes.php:0

   5

[DDC-133] Complete implementation for schema support.

Sun, 8 Aug 2010 09:09:04 +0000

Complete implementation for schema support.

[DDC-385] Change behaviour if fully qualified classname is passed in as string

Sun, 8 Aug 2010 09:05:25 +0000

If one calls $em->getRepository('\Entity') (leading \ !) then Doctrine's behaviour is quite undefined, as it would result e.g. in a "mapping file '.entity.dcm.yml' not found" error. (leading dot!)

PHP, however, seems to allow the leading \, but Doctrine does not. In fact, the leading \ is not necessary as classnames in strings are always fully qualified.

So Doctrine should either:

1.) Throw an exception stating that using a leading backslash is prohibited
2.) Simply strip it.

[DDC-675] EntityManager->find() returns detached (or otherwise unmanaged) object.

Sun, 8 Aug 2010 09:05:07 +0000

The find method seems to be broken. Returned objects are not managed according to the EntityManager. Fetching the same object via findAll() works.

$e = $em->find('\net\jay\products\doctrine\ProductEntityType', 1);
print "Class: " . get_class($e) . "<br>";
print "Contained: " . ($em->contains($e) === true ? 'Yes' : 'No');

This gives me:

Class: net\jay\products\doctrine\ProductEntityType
Contained: No

[DDC-650] $data using wrong index in UnitOfWork::createEntity() in one to one assoc

Sun, 8 Aug 2010 08:37:04 +0000

It looks like $data is using the wrong index ($srcColumn) in UnitOfWork::createEntity() line 1834 (1854 in github repo, it seems my IDE can't count ) to get the $joinColumnValue. Since $data contains the camelized field names and $srcColumn is the actual field name, should it be:

+ $joinColumnValue = $data[$class->fieldNames[$srcColumn]];
- $joinColumnValue = $data[$srcColumn];

[DDC-419] Problem when I make a INNER JOIN between 2 classes

Dependency — Sun, 8 Aug 2010 07:17:16 +0000

I hae some problems when I make a inner join between 2 classes, one of these classes makes join to others 2 classes in the same time and when I try to make a inner to this class, it's not coming like a object, but object Id...

I don't know why its happening..

I make a test case..there're all the classes and yml that show my problem..it's on ItemPregaoTest.php.. just need to run phpunit in this file..

[DDC-383] Setting Column name doesn't work predictably in associations

Sun, 8 Aug 2010 07:16:38 +0000

Setting a column name that is different from the property name yields errors in associations (e.g. in a one to one association I get "Undefined index: shipping_id in /var/www/wetawa/library/Doctrine/ORM/UnitOfWork.php on line 1782 Call ")

...
    /**
     * @Column(type="bigint", name="shipping_id")
     *
     * @var integer
     */
    protected $shippingId=0;
    /**
     * @OneToOne(targetEntity="Shipping")
     * @JoinColumn(name="shipping_id", referencedColumnName="id")
     * 
     * @var Shipping
     */
    protected $shipping;

The only way I've been able to get associations to work is by using the default naming so $shipping_id instead of $shippingId

[DDC-700] Proxy class is created for MappedSuperclass class

Sun, 8 Aug 2010 06:05:48 +0000

When having abstract class as Mapped Superclass the proxy class is created without the "abstract" keyword which raises fatal PHP error "Class %proxyClassName% contains 1 abstract method and must therefore be declared abstract or implement the remaining methods" when read.

I think there is no need to generate the proxy classes for classes marked as @MappedSuperclass at all.

[DDC-654] Unused lines of code in Doctrine\ORM\Query\AST\Functions

Sun, 8 Aug 2010 05:49:51 +0000

The majority of the classes contains a line that does notthing

$lexer = $parser->getLexer();

[DDC-709] Doctrine-cli should check @OrderBy() taget existency

Sun, 8 Aug 2010 05:39:59 +0000

Doctrine-cli orm:validate-schema should check schema for common typo mistakes as much as possible. Unknown target attribute passes ok. It's not expected behaviour.

[DDC-645] XML schema missing change-tracking-policy

Sun, 8 Aug 2010 05:32:55 +0000

Hi,

XML schema is missing change-tracking-policy element:

<entity name="Doctrine\Tests\Models\ECommerce\ECommerceCart" table="ecommerce_carts">
        <change-tracking-policy>DEFERRED_IMPLICIT</change-tracking-policy>
        <field name="payment" type="string" column="payment" length="50" precision="0" scale="0"/>

Thank you