Databases
StackOverflow2013
Postsdbo
PODoctrine 2. How to force entity from proxy
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODoctrine 2. How to force entity from proxy
    primarykey
    data
    text
    <p>I have 3 entities:</p> <pre><code>/** * @ORM\Entity * @ORM\Table(name="table_a") */ class A { /** * @ORM\Id * @ORM\Column(type="integer") * @ORM\GeneratedValue */ protected $id; /** * ORM\OneToMany(targetEntity="B", mappedBy="entityA") */ protected $entitiesB; /** * ORM\OneToMany(targetEntity="C", mappedBy="entityA") */ protected $entitiesC; /** * @ORM\Column(type="string") */ protected $name; } /** * @ORM\Entity * @ORM\Table(name="table_b") */ class B { /** * @ORM\Id * @ORM\Column(type="integer") * @ORM\GeneratedValue */ protected $id; /** * ORM\ManyToOne(targetEntity="A", inversedBy="entitiesB") */ protected $entityA; /** * @ORM\Column(type="date") */ protected $date; } /** * @ORM\Entity * @ORM\Table(name="table_c") */ class C { /** * @ORM\Id * @ORM\Column(type="integer") * @ORM\GeneratedValue */ protected $id; /** * ORM\ManyToOne(targetEntity="A", inversedBy="entitiesC") */ protected $entityA; /** * @ORM\Column(type="string") */ protected $description; } </code></pre> <p>And I have the following situation:</p> <pre><code>$eB = $repositoryB-&gt;find(1); $eA = $eB-&gt;getEntityA(); // $eA will be a proxy $eC = new C(); $eC-&gt;setDescription('XXXXXXXXXX') -&gt;setEntityA($eA); </code></pre> <p>This will generate an error because $eA is a proxy not an entity. Even if I try:</p> <pre><code>$eB = $repositoryB-&gt;find(1); $eA = $repositoryA-&gt;find(1); $eC = new C(); $eC-&gt;setDescription('XXXXXXXXXX') -&gt;setEntityA($eA); </code></pre> <p>Will still get an error because once you have fetched a B entity it will automatically fetch a proxy of A entity. And when you try to fetch the A entity with the same identifier as the proxy Doctrine will return the proxy object from the Identity Map because you can not have two objects (one proxy and one Entity) for the same db record.</p> <p>So is there a way to force retrieving an entity from its proxy? Or another way to set an association, by id not by entity?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USCalin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThe code which you wrote should work, please post the relevant errors that you are talking about.
      singulars
      1. PODoctrine 2. How to force entity from proxy
      1. USFlip
    2. COI did'nt post the error because it will be confusing and irelevant to the problem. Here is the error: "Fatal error: Uncaught exception 'Doctrine\ORM\ORMInvalidArgumentException' with message 'A new entity was found through the relationship 'A#entitiesB' that was not configured to cascade persist operations for entity: . To solve this issue: Either explicitly call EntityManager#persist() on this unknown entity or configure cascade persist this association in the mapping for example @ManyToOne(..,cascade={"persist"}).' in \library\Zend\Controller\Plugin\Broker.php on line 336"
      singulars
      1. PODoctrine 2. How to force entity from proxy
      1. USCalin
    3. COThe problem is that $eA is a proxy not an entity. If i do $eA = $repositoryA->find(xx), where xx is a different identifier than the one in the proxy class it will be an entity and the code will work. The problem is that i can not have 2 object for the same record. I have also tried getting $eB by query builder like "SELECT b, a FROM B b JOIN b.entityA a WHERE b.id = 1" but it still gives me a proxy
      singulars
      1. PODoctrine 2. How to force entity from proxy
      1. USCalin
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload