Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h2>Solution</h2> <p>What you're looking for is <a href="http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/working-with-associations.html#orphan-removal">orphan removal</a>.</p> <p>You can read on if you'd like details on why your current situation isn't working.</p> <h2>Cascade woes</h2> <p>The cascade operation won't do what you want unfortunately. The "cascade=[remove]" just means that if the entity object is removed then doctrine will loop through and remove all child attributes as well:</p> <pre><code>$em-&gt;remove($entity); // doctrine will basically do the following automatically foreach ($entity-&gt;getAttributes() as $attr) { $em-&gt;remove($attr); } </code></pre> <h2>How to do it manually</h2> <p>If you needed to remove an attribute from an entity you'd delete the attribute like so:</p> <pre><code>$entity-&gt;getAttributes()-&gt;removeElement($attr); $em-&gt;remove($attribute); </code></pre> <h2>Solution details</h2> <p>But, to do that automatically we use the orphan removal option. We simply tell doctrine that attributes can only belong to entities, and if an attribute no longer belongs to an entity, simply delete it:</p> <pre><code>/** * @ORM\OneToMany(targetEntity="Attribute", mappedBy="entity", orphanRemoval=true, cascade={"persist", "remove", "merge"}) **/ protected $attributes; </code></pre> <p>Then, you can remove the attribute by simply doing this:</p> <pre><code>$entity-&gt;getAttributes()-&gt;removeElement($attr); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PODoctrine 2 Entities Relations Remove
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USradnan
    1. USradnan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODoctrine 2 Entities Relations Remove
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI have it partially working now thanks to you. There is just a little thing that isn't working properly. With the attribute entity set to null and removed from the array collection of the entity, it just sets the attribute entity id to null in the database and does not remove it when I persist the entity.
      singulars
      1. PO
      1. USNicholas Charbonneau
    2. COmy apologies. i've updated my answer. you're not supposed to unset the entity, you just need to remove it from the attributes collection.
      singulars
      1. PO
      1. USradnan
 

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