Why does Doctrine\ORM\Configuration's “DoctrineProxies” Object contain the Universe?

问题

In my ORM code I have an Entity with a field fined like so:

//part of entity class Item:
/** @Column(name="product_id", type="integer") */
private $productId;

I then executed this code:

//3 lines ~straight out of Doctrine configuration to get EntityManager
include 'config/doctrine-config.php';
$config = Setup::createAnnotationMetadataConfiguration($paths, $isDevMode);
$em = EntityManager::create($dbParams, $config);

//my own code to retrieve an entity instance:
$instance = $em->find(Item::class, 2);
print_r($instance);

And this is the output I get (skipping few other similar properties):

Application\Entity\Item Object
(
    [id:Application\Entity\Item:private] => 2
    [description:Application\Entity\Item:private] => Product Kit
    [productId:Application\Entity\Item:private] => -1
)

Note how there are 6 (six) lines above that came out of print_r() function.

And everything was fine, Until

Next, I have changed the $productId column to ManyToOne Relationship on my Item Entity class, like so:

/** 
 * @ManyToOne(targetEntity="Product", inversedBy="id")
 * @JoinColumn(name="product_id", referencedColumnName="id")
 */
private $productId;

I ran the same code.

OUT CAME THE UNIVERSE OF 2,392,600 LINES, WHAT?

Two million, three hundred and ninety two thousand, six hundred lines lines of print_r output.

looking at the print-out I see that DoctrineProxies\__CG__\Application\Entity\Product Object contains 2,392,564 lines printed by print_r

Question:

What is exactly in this object and why is it so big as to take up nearly 300Mb of disk space when printed out?

I cannot help but wonder if such complexity is apt to cause performance issues in every-day code. For example, I am not printing out the contents of the $instance variable in my every-day code, but I surely return the humongousness from a method call. Does that mean it is a 300Mb variable that gets passed from i.e. the $em->find(Item::class, 2); call above?

(Very) Partial Listing

回答1:

You can't dump a proxy object without XDebug or similar tools (which limit the dumped object size).

The problem is really, really simple:

Proxy -> references EntityManager -> references UnitOfWork -> contains Proxy

This obviously leads to a recursive data-structure dump, which in turn leads to a mess any time you try to dump it without sensible limits.

回答2:

DoctrineProxies\__CG__\Application\Entity\Product is a proxy class... which means that doctrine doesn't actually fetch the entity from the database (for performance) unless it is needed (i.e. calling $product->getName() those proxy Classes are in a recursive loop with eachother and are VERY large as you saw... most of the information there you don't really need unless you are diving deep ... you should never use print_r ... in the new symfony 2.7+ i think there is a function called dump() in debug mode ... if you use that to print the entity it has loop protection and it just shows reference numbers ... you can also use the \Doctrine\Common\Util\Debug::dump() that also will print out a smaller list than 2^234234234 lines ...

来源：https://stackoverflow.com/questions/37076711/why-does-doctrine-orm-configurations-doctrineproxies-object-contain-the-unive

标签

php

symfony

orm

doctrine-orm

proxy-classes