Databases
StackOverflow2013
Postsdbo
POHow do I know that OneToMany relation has been changed?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do I know that OneToMany relation has been changed?
    primarykey
    data
    text
    <p>I have the following entities:</p> <pre><code>class Person { /** * @var integer * * @ORM\Column(name="id", type="integer") * @ORM\Id * @ORM\GeneratedValue(strategy="AUTO") */ private $id; /** * * @ORM\OneToMany(targetEntity="PersonEmail", mappedBy="person", cascade={"persist", "remove"}) */ private $emails; /** * @var datetime $updated * * @ORM\Column(type="datetime") */ private $updated; } </code></pre> <p>.</p> <pre><code>class PersonEmail { /** * @var integer * * @ORM\Column(name="id", type="integer") * @ORM\Id * @ORM\GeneratedValue(strategy="AUTO") */ private $id; /** * @var string * * @ORM\Column(name="email", type="string", length=255) */ private $email; /** * @ORM\ManyToOne(targetEntity="Person", inversedBy="emails") * @ORM\JoinColumn(name="person_id", referencedColumnName="id", onDelete="CASCADE") */ private $person; } </code></pre> <p>I use Symfony2 form builder to create forms. After the form is submitted I call <code>$form-&gt;bind($request)</code>. And my question is: how do I know that the emails are changed (inserted, updated or deleted) before I save the Person entity? I need it because I want to update Person::$updated field. I can do it when the Person entity is modified itself using PreUpdate lifecycle callback, but how can I update this field when only email list was changed? Predicting the easiest answer: I would like to avoid updating this field when nothing is changed at all.</p> <p>Updating the Person entity in the PersonEmail's lifecycle callback is not possible, since the Person entity is already processed at that moment.</p> <p>Controller code (not sure if it helps):</p> <pre><code>/** * * @Template() */ public function editAction($id, Request $request) { $repository = $this-&gt;getDoctrine()-&gt;getRepository('AcmeBundle:Person'); $person = $repository-&gt;find($id); if (!$person) { throw $this-&gt;createNotFoundException('No person found for id '.$id); } if ($request-&gt;isMethod('POST')) { $form-&gt;bind($request); if ($form-&gt;isValid()) { $em = $this-&gt;getDoctrine()-&gt;getEntityManager(); $em-&gt;flush(); } } return array('form' =&gt; $form-&gt;createView(), 'person' =&gt; $person); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDenis V
    1. USDenis V
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow do I know that OneToMany relation has been changed?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow do I know that OneToMany relation has been changed?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow do I know that OneToMany relation has been changed?
      1. This table or related slice is empty.
      1. VTClose
    1. COCan you post your controller's code?
      singulars
      1. POHow do I know that OneToMany relation has been changed?
      1. UScheesemacfly
    2. CO@cheesemacfly : I updated the question
      singulars
      1. POHow do I know that OneToMany relation has been changed?
      1. USDenis V
    3. COWhy don't you in your controller check that `$originalperson->emails === $person->emails` after `$form->bind($request)` and if not, just call `$person->updated = new \DateTime()`?
      singulars
      1. POHow do I know that OneToMany relation has been changed?
      1. UScheesemacfly
 

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