[DDC-1974] @OneToOne and @InheritanceType cause Duplicate Key Errors when changing the entity

Wed, 29 Aug 2012 13:23:34 +0000

<?php

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

    /**
     * @OneToOne(targetEntity="B", mappedBy="a")
     */
    private $b;
}

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

    /**
     * @OneToOne(targetEntity="A", inversedBy="b")
     */
    private $a;
}

/** 
 * @Entity 
 */
class B_sub extends B
{
    /** @Column(type="string") */
    private $sub;
}

/** 
 * @Entity 
 */
class B_sub2 extends B
{
    /** @Column(type="string") */
    private $sub2;
}

The code creates several tables and a UNIQUE KEY constraint on B (a_id)

Now trying to accomplish the following sequence of action:

$B = new B_sub();
$A = new A();

$A->set('b', $B);
$B->set('a', $A);

$em->persist($A);
$em->persist($B);
//works fine and creates the correct DB entries
$em->flush();

$B_new = new B_sub2();
$B_old = $A->get('b');
$A->set('b', $B_new);
$B_new->set('a', $A);

$em->remove($B_old);
$em->persist($A);
$em->persist($B_new);
//does not work, because B_new is inserted first and fails the UNIQUE KEY constraint (both B_new and B_old refer to A)
$em->flush();

The result is a "Duplicate entry '1' for key 'UNIQ_7F6BFCEBE26CCE03'"

[DDC-1968] CommitOrderCalculator fails to calculate right order for mixing one-to-many and one-to-one relations

Sun, 6 Jan 2013 18:41:36 +0000

I have 2 classes. Zone and Rotator.
Zone relates to Rotator as One-to-Many. And Zone COULD realte to Rotator as One-to-One. Here is code snippet:

 
class Zone
{
    /**
     * @var integer $id
     *
     * @ORM\Column(name="id", type="integer")
     * @ORM\Id
     * @ORM\GeneratedValue(strategy="AUTO")
     */
    private $id;

    /**
     * @ORM\OneToMany(targetEntity="Rotator", mappedBy="zone", cascade={"persist", "remove", "merge"}, orphanRemoval=true)
     * @ORM\OrderBy({"id" = "ASC"})
     */
    private $rotators = array();

    /**
     * @var Rotator $mainRotator
     *
     * @ORM\OneToOne(targetEntity="Rotator")
     * @ORM\JoinColumn(name="mainRotatorId", referencedColumnName="id")
     */
    private $mainRotator;

    /**
     * @var int $mainRotatorId
     *
     * @ORM\Column(name="mainRotatorId", type="integer", nullable="true")
     */
    private $mainRotatorId;
}

 
class Rotator
{
    /**
     * @var integer $id
     *
     * @ORM\Column(name="id", type="integer")
     * @ORM\Id
     * @ORM\GeneratedValue(strategy="AUTO")
     */
    private $id;

    /**
     * @var Zone $zone
     *
     * @ORM\ManyToOne(targetEntity="Zone")
     * @ORM\JoinColumn(name="zoneId", referencedColumnName="id")
     */
    private $zone;

    /**
     * @var int $zoneId
     *
     * @ORM\Column(name="zoneId", type="integer")
     */
    private $zoneId;
}

When I delete only Zone - calculator works fine. But it fails if I delete entity Site, that relates to Zone as one-to-many (and have a lot of other raltions, so I don't write it here).

As I look through the code, I see CommitOrderCalculator doesn't distiguish mandatory many-to-one relation from optional one-to-one one.

PS this code hadn't been changed since 2.0, so this bug should be reproducable for master.

Doctrine Project

[DDC-1974] @OneToOne and @InheritanceType cause Duplicate Key Errors when changing the entity

[DDC-1968] CommitOrderCalculator fails to calculate right order for mixing one-to-many and one-to-one relations